SHAR Production Metadata MCP
OfficialServer 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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_production_manifestA | Checks required project metadata, production stage, and declared rights status. Does not read files, call networks, or publish data. |
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
With only one tool, there is no possibility of confusing it with another. The tool's purpose is clearly defined in its description, leaving no ambiguity.
The single tool follows a clear verb_noun pattern: validate_production_manifest. There are no other tools to introduce inconsistency, so naming is perfectly coherent.
A single tool feels thin for a server named 'Metadata MCP,' which could imply a broader scope. However, the tool's narrowly defined validation purpose means one tool may be reasonable, but it falls in the borderline range.
The tool covers the core validation functionality for production metadata, checking project metadata, stage, and rights status. However, the server name suggests a broader metadata management role, so additional operations like retrieval or update might be expected, creating a minor gap.