MCP Specification 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 | {} |
| logging | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mcpjam_search_mcp_specC | Search the MCP specification document for relevant content |
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 confusion between tools, so disambiguation is perfect.
The single tool name follows a clear pattern (prefix_verb_noun) and is internally consistent.
One tool is borderline thin for a server; while it may be sufficient for a simple search utility, typical specification servers offer more operations.
The server only provides search, missing obvious operations like retrieving specific sections or listing contents, making the toolset incomplete for comprehensive specification interaction.