Update README and requirements files for clarity and dependency manag…

[MiguelElGallo]

…ement

Purpose

• ...

Does this introduce a breaking change?

[ ] Yes
[ ] No

Pull Request Type

What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

• Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

• Test the code

What to Check

Verify that the following are valid

• ...

Other Information

[Copilot]

Pull Request Overview

This PR updates the README documentation for improved clarity and removes the auto-generated requirements.txt file to rely on dynamic dependency resolution. The changes focus on fixing formatting issues, correcting numbering sequences, and improving the documentation structure while removing the pinned dependency versions.

Key Changes

• Removes the auto-generated requirements.txt file with pinned dependency versions
• Fixes README formatting issues including numbering sequence and bullet points
• Adds information about the MCP inspector web interface

Reviewed Changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.

File	Description
src/requirements.txt	Complete removal of auto-generated pinned dependencies file
README.md	Documentation improvements including fixed numbering, formatting corrections, and added MCP inspector information

Comments suppressed due to low confidence (1)

[Copilot]

The MCP inspector URL appears incorrect. Based on the coding guidelines, the MCP inspector runs locally at http://127.0.0.1:6274 during development with 'mcp dev app.py', not on the deployed Azure App Service. The documentation should clarify this distinction between local development and production deployment.

Suggested change

	The server also includes the MCP inspector, which is a web interface to inspect the MCP messages. You can access it at: (<http://yourapp.azurewebsites.net/#resources>)
	> **Note:** The server also includes the MCP inspector, a web interface to inspect MCP messages. This inspector is only available during local development at [http://127.0.0.1:6274](http://127.0.0.1:6274) when running `mcp dev app.py`. It is **not** accessible on the deployed Azure App Service.