Skip to main content
Glama

agent-tools (x402 + MCP + A2A directory)

get_mcp_server

Read-only

Get the full card for one MCP server by slug.

Args:
    slug: MCP server slug as returned by `search_mcp_servers` items.

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
slugYesMCP server slug as returned by `search_mcp_servers` items.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / slug / description
      Added value: +"MCP server slug as returned by `search_mcp_servers` items."
  2. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, covering the safety profile. The description adds little behavioral context beyond 'full card,' such as error behavior or lookup scope, but the annotations and output schema carry most of that burden.

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 front-loaded and efficient, with the core action stated first and the single argument documented briefly. There is no wasted text.

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

Completeness5/5

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

For a simple one-parameter read tool with annotations, full schema coverage, and an output schema, the description provides enough context to invoke it correctly. It identifies the resource, the required identifier, and where that identifier comes from.

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 description coverage is 100%, so the parameter is already well documented. The description repeats the same slug meaning without adding format, validation, or edge-case details beyond 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 states a specific verb and resource: 'Get the full card for one MCP server by slug.' It clearly distinguishes this lookup tool from the sibling search_mcp_servers by emphasizing a single server and its full card.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implicitly tells the agent to call this after obtaining a slug from search_mcp_servers items, giving clear usage context. However, it does not explicitly state when not to use this tool or name alternatives beyond the slug source.

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.