Skip to main content
Glama

Get one MCP server

get_server
Read-onlyIdempotent

Use before connecting a server, or when the user names one: registry data, latest measurements, declared risk, rank parts, connection URLs and tools of one server.

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": {
      "name": "<name>"
    },
    "name": "get_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesRegistry name, e.g. com.example/server

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description adds real context by itemizing the payload (registry data, latest measurements, declared risk, connection URLs, tools), which tells the agent what a call actually yields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence pairing the usage trigger with the returned content, with no filler. 'rank parts' is mildly opaque jargon that costs a little clarity.

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?

With no output schema, the description carries the burden of describing return values and does so by listing the returned sections. It omits error behavior for unknown names, which is the main remaining gap for a single-param lookup.

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 'name' property already carries the registry-name example (com.example/server), so the description adds nothing about the parameter. Baseline 3 applies when the schema does the full job.

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?

Names a specific verb and resource (fetch one MCP server) and enumerates what comes back: registry data, measurements, declared risk, rank parts, connection URLs, tools. The phrase 'of one server' distinguishes it from search_servers, though no sibling is named explicitly.

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?

'Use before connecting a server, or when the user names one' gives concrete triggering conditions, which is more than most definitions offer. It stops short of naming the alternative (search_servers) for the case where the user has a description rather than a name.

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