XSD Retrieval MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| retrieve_xsdC | Retrieve an XSD file from a URL or file path |
| validate_xsdB | Validate if the retrieved content is a valid XSD |
| list_xsd_elementsB | Extract and list elements defined in an XSD |
| get_mcp_server_infoA | Get MCP server information including name and version |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct function: server info, XSD retrieval, validation, and element listing. There is no overlap in purpose.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., retrieve_xsd, validate_xsd).
With only 4 tools, the server is well-scoped for its purpose of XSD retrieval and basic operations. Each tool is necessary and none is redundant.
Covers retrieval, validation, and element listing. Missing more granular element detail extraction, but the core workflow is complete for a retrieval-focused server.