Skip to main content
Glama

Details of a hosted MCP server

info
Read-only

Displays a hosted server's description, policy, state, recent redacted stderr, and active instructions for inspecting its configuration and runtime status.

Instructions

Shows a hosted server's description, policy, state, recent (redacted) stderr and, when on, its full instructions.

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": "info"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesServer name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavioral detail: stderr is redacted and full instructions appear only 'when on.' It does not describe error behavior for an invalid or missing server name.

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?

A single sentence with no filler, front-loading the verb and then listing the highest-value return fields. Every clause carries information an agent would otherwise have to discover by calling the tool.

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 must convey return content, and it does so field by field, including the conditional instructions disclosure. The remaining gap is failure behavior (what happens if the name does not resolve), which is minor for a read-only inspection tool.

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?

There is a single parameter with 100% schema description coverage ('Server name'), so the schema already carries the burden. The description only establishes that the name identifies a hosted server, adding no format, lookup, or failure semantics beyond that.

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 gives a specific verb-plus-resource ('Shows a hosted server's...') and enumerates exactly what is returned: description, policy, state, redacted stderr, and instructions. That enumeration makes it clearly distinct from the sibling mutation tools (enable/disable/restart) and the list tool (servers), 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 required 'name' parameter plus the field enumeration signal 'inspect one existing server.' There is no statement about when to prefer it over 'servers' or what to do when the server is unknown, so the agent must infer the selection rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools