Get full metadata for a specific MCP server by its reverse-DNS registry name (e.g. io.github.username/server-name). Returns all versions, remotes, packages, and tools.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Reverse-DNS registry name of the server (e.g. io.github.username/server-name) |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It discloses return content (all versions, remotes, packages, tools) but does not mention error behavior (e.g., server not found), authentication requirements, or potential side effects. It adds some context but lacks important behavioral details.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that is front-loaded with the action and resource, and every phrase adds value. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple single-parameter lookup with no output schema, the description sufficiently explains the return value scope. It could be improved with edge-case handling, but overall it is complete enough for basic use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema fully describes the single 'name' parameter with an example, and the description repeats the same example without adding new meaning. Per the baseline for 100% schema coverage, this is adequate but not enhanced by the description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves full metadata for a specific MCP server by its reverse-DNS name, distinguishing it from sibling tools that list or search. It also specifies the return content (versions, remotes, packages, tools), leaving no ambiguity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies use when you have a known reverse-DNS name and need detailed metadata, which distinguishes it from listing or searching. However, it does not explicitly mention alternatives or when not to use this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool serves a distinct purpose: searching by keyword, listing all servers, and fetching detailed metadata for a specific server. There is no overlap in functionality or ambiguity in choosing the right tool.
All tool names follow a consistent verb_noun pattern with snake_case: get_mcp_server_details, list_mcp_servers, search_mcp_registry. The verbs (get, list, search) clearly indicate the action, and nouns describe the target.
Three tools is well-scoped for a registry search and discovery service. Each tool is essential for the core workflow, and the count fits comfortably within the ideal range.
The tool set covers the full lifecycle of registry exploration: search to find servers, list to browse all, and get details to inspect a specific server. There are no obvious gaps for the stated purpose of browsing and retrieving MCP server information.