Skip to main content
Glama

get_mcp_server

Read-onlyIdempotent

Retrieve an external MCP server configuration by UUID so clients can identify and connect to the correct server.

Instructions

Retrieve an external MCP server configuration by its UUID.

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

Input Schema

NameRequiredDescriptionDefault
mcp_server_idYesMCP server UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.4
    • changedInput schema / properties / mcp_server_id / description
      Previous value: -"UUID do MCP server"New value: +"MCP server UUID"
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/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 and repeatability are covered elsewhere. The description adds only that the object is a server "configuration"; it says nothing about whether secrets are included, whether missing IDs error or return null, or any permission requirements. That is acceptable against the annotation baseline but not generous.

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 twelve-word sentence with the lookup key front-loaded after the verb; every clause earns its place and there is 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 whose annotations already establish safety and idempotency, the definition covers what is needed to select and invoke it. The remaining gap is the absence of any output schema combined with no indication of what the returned configuration contains (e.g. whether credentials are masked).

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% and the single parameter is already documented as "MCP server UUID", so the description only echoes the same idea via "by its UUID". No additional format, validation, or sourcing guidance is layered on top of the schema.

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?

States a specific verb and resource ("Retrieve an external MCP server configuration") plus the lookup key ("by its UUID"), which cleanly separates it from list_mcp_servers and the create/update/delete/test siblings. It never names an alternative explicitly, so it stops short of full sibling differentiation.

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: "by its UUID" signals a single-record fetch keyed on an identifier, which an agent can reasonably contrast with a list operation. There is no explicit statement of when to prefer this over list_mcp_servers or what to do when the UUID is unknown.

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