get_mcp_server
Get a complete structured server record, endpoints, tools, evidence-based trust, risks, warnings and install options.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
RMCP
by dev.rmcp
TDQS
A3.6/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears full responsibility. It indicates the tool returns data (read operation) but does not disclose authorization requirements, rate limits, or any side effects. The description lists what is included but lacks details on behavioral traits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence of 12 words, front-loaded with the action 'Get'. No redundant information; every word contributes to understanding the tool's output.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description lists multiple components (endpoints, tools, trust, risks, etc.) but lacks details on error handling, availability, or output structure. No output schema exists to compensate. The description is adequate but not thorough for a tool returning complex structured data.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description does not elaborate on the 'id' parameter beyond implicit identification. It does not specify the format or source of the ID (e.g., UUID, name), leaving ambiguity. The description adds minimal value over the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves a 'complete structured server record' including endpoints, tools, trust, risks, warnings, and install options. The verb 'Get' and the detailed list of components make the purpose unambiguous. It distinguishes from siblings like get_mcp_endpoint, which is more specific.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is used when a full server record is needed, but it does not explicitly compare with siblings or state when not to use it. No guidance on prerequisites or alternatives is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.5/5.0
Disambiguation5/5
Each tool targets a distinct operation: checking endpoints, comparing servers, retrieving install instructions, getting endpoint/server/tool details, or searching. No two tools have overlapping purposes.
Naming Consistency5/5
All tools follow a verb_noun pattern in snake_case (e.g., check_mcp_endpoint, search_mcp_tools). The naming is uniform and predictable.
Tool Count5/5
With 8 tools, the set covers all necessary query, retrieval, and search functions for an MCP registry without excess. The count feels well-scoped.
Completeness4/5
The tools cover all major read operations for the registry domain, including retrieval of endpoints, servers, tools, and search. Minor gaps like update/delete operations are absent but consistent with a supposedly static index.