feat: Add manifest validation tool

[dimovpetar]

No description provided.

[coveralls]

Pull Request Test Coverage Report for Build 19034241365

Details

• 89 of 93 (95.7%) changed or added relevant lines in 5 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.5%) to 81.894%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/tools/run_manifest_validation/runValidation.ts	48	52	92.31%

Totals
Change from base Build 19030937854:	0.5%
Covered Lines:	1090
Relevant Lines:	1236

---

💛 - Coveralls

[alexandar-mitsev]

Looks good to me

[RandomByte]

Have you considered adding the @ui5/manifest npm package as a dependency instead of dynamically fetching the schema?

I guess the benefit of this approach is that the user will always validate against the latest version of the schema. But actually this could be a drawback as well since the MCP Server will become less deterministic.

A manifest.json that validates fine today might show errors tomorrow if a newly published schema makes respective changes. We should at least clarify with the maintainers of ui5-manifest whether pointing directly to the main branch (usually used for development) is fine here.

[RandomByte]

Just like for the create tool, please normalize the path using the Context:

mcp-server/src/tools/create_integration_card/index.ts

Line 27 in f5035db

const normalizedBasePath = await context.normalizePath(params.basePath);