Skip to main content
Glama

get_tool

Read-onlyIdempotent

Full Agent Tool Card for one ID (usually not needed: search_tools already returns best_pick.use_it to set it up). Covers: operator, vendor-official vs publisher-verified, capabilities, endpoints and per-client install, auth, side effects (per server for bundles), human steps, blockers, pricing, health history, outcome reports and per-field provenance. Unknown IDs return isError with error_code not_found.

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

Input Schema

NameRequiredDescriptionDefault
idYese.g. mcp:com.stripe/mcp; see resolve_tool
stageNooptional, self-declared
clientNooptional, e.g. claude-code, cursor, my-agent
agent_typeNooptional, self-declared

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description goes beyond them by specifying the failure contract: unknown IDs return isError with error_code not_found. It also flags that side effects are reported per server for bundles, which is real behavioral context an agent could otherwise guess wrong.

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?

Front-loaded with the core purpose and the opt-out hint before the enumeration. The long "Covers: ..." list is dense but every item describes a returned section; a reader can skim it. Slightly list-heavy, but no wasted sentences.

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 enumeration of covered sections (operator, verification tier, auth, side effects, blockers, pricing, provenance) does the job of describing return content, and the error case is spelled out. Missing only structural detail, such as how large the payload is or whether sections can be absent, which is minor for a single-record read.

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%, so id, stage, client and agent_type are already documented, and the description adds only indirectly ("per-client install" hints that client shapes the card). It never explains how stage or agent_type alter the returned content, so it does not beat the schema baseline.

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?

States a specific verb+resource ("Full Agent Tool Card for one ID") and immediately distinguishes itself from the sibling that overlaps: the parenthetical points at search_tools' best_pick.use_it. An agent can tell exactly which lookup produces the full card without opening the schema.

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?

"usually not needed: search_tools already returns best_pick.use_it to set it up" gives a clear negative condition and names the alternative. It leaves the positive trigger implicit (call this when you need the full card, e.g. auth/side effects/blockers), so a bit of inference remains, but routing is clear.

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