Skip to main content
Glama

allMCPservers directory

Get an MCP server's details

get_mcp_server
Read-onlyIdempotent

One server's full profile: description, remote endpoint or package to install, required headers and environment variables, repository, documentation and the official listings it comes from.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_mcp_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe server's slug from search results, or its allmcpservers.com profile link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover read-only, closed-world, and idempotent characteristics, so the description cannot earn credit there. It does add value by disclosing the breadth of the payload — including provenance via 'the official listings it comes from' — which matters since there is no output schema. It omits error behavior for an unknown slug, which keeps it from a 5.

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?

One compact sentence, front-loaded with the resource and then a tight enumeration of contents. Nothing redundant and no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with full schema coverage and annotations carrying the safety profile, the description covers the essential question of what comes back. Only the invalid-slug behavior is left unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single slug parameter is already documented as coming from search results or a profile link. The description adds no format or resolution detail beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific resource ('One server's full profile') and enumerates the returned components — endpoint/package, headers, env vars, repo, docs, listings. It is clearly distinguishable from the sibling search/compare/list tools, though it never names an alternative explicitly.

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?

Usage is only implied: the schema note 'slug from search results' hints at a search-then-fetch workflow, but the description itself gives no explicit when-to-use, no when-not-to-use, and no pointer to siblings like search_mcp_servers or compare_mcp_servers.

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.

Resources