Aspose MCP Catalog Orchestrator
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| update_product_mcpB | Propose a validated product or platform MCP metadata update for human review. |
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 1 tool
Only one tool exists, so there is no possibility of confusion. The tool's purpose is clearly distinct by default.
The single tool name follows a clear verb_noun pattern (update_product_mcp), which is consistent and predictable.
One tool for a catalog orchestration server is far too few; the scope implies a broader workflow requiring multiple management actions.
Only an update proposal tool is provided, with no listing, retrieval, deletion, or approval operations. This severely under-covers the stated orchestration domain.