Allotrope 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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_field_mapA | Validate a field mapping file produced by a custom converter script. |
| validate_asm_schemaA | Validate an ASM JSON document against an Allotrope JSON Schema. |
| fetch_asm_documentA | Fetch a raw ASM JSON document from purl.allotrope.org. |
| list_asmsA | List all available Allotrope Simple Models (ASMs). |
| describe_asmA | Return the metadata for a specific ASM model by name. |
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 5 tools
Each tool targets a distinct resource and action: validate_field_map checks field mappings, validate_asm_schema validates an ASM document against a schema, fetch_asm_document downloads a raw ASM document, list_asms enumerates models, and describe_asm provides metadata for a specific model. There is no meaningful overlap in purpose.
All tool names follow a consistent verb_noun pattern with snake_case: validate_field_map, validate_asm_schema, fetch_asm_document, list_asms, describe_asm. The minor difference in singular/plural (asm/asms) is natural and does not create confusion.
Five tools is well within the ideal 3-15 range and each tool serves a clear, non-redundant function. The count feels appropriately scoped for a server focused on ASM validation and metadata retrieval.
The server covers the core workflows of discovering ASM models, fetching documents, validating schemas, and validating field maps. A minor gap is the lack of a tool to fetch schemas directly, but this can be worked around since validate_asm_schema accepts a local schema path.