Skip to main content
Glama

magne.tools

Get a tool

get_tool
Read-only

One tool's card by id: tagline, use cases, pricing, auth, links and a code snippet, with its tool page URL and its tasks.

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
idYesA tool id from find_tools_for_task, e.g. "resend".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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, so the safety profile is covered and the bar is lower. The description adds real value by disclosing the shape of the payload (pricing, auth, links, snippet, page URL, tasks). It says nothing about failure behavior for a bad or stale id, which is the main remaining unknown for a lookup tool.

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?

One compact sentence that front-loads the identifying scope ('one tool's card by id') before the field list. Nothing is redundant, though the trailing field enumeration makes it read as a fragment rather than a stated action.

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 the return value and does so thoroughly, listing the card's fields plus the page URL and associated tasks. The only material gap for a one-parameter read tool is the absence of any note about invalid ids or missing tools.

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, and the schema already explains the id's provenance with a concrete example ('resend'). The description's 'by id' adds no syntax, format, or constraint information beyond that, so baseline 3 applies.

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 names the resource ('one tool's card') and the lookup key ('by id'), and enumerates what the card contains (tagline, use cases, pricing, auth, links, code snippet, page URL, tasks). That is enough to separate it from search_tools and find_tools_for_task, which return sets rather than a single record. It stops short of a clean verb phrase, but the intent is unambiguous.

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 id' plus the schema note that the id comes from find_tools_for_task suggests a follow-up detail fetch after discovery. The description itself never states when to call this instead of search_tools or list_tasks, nor what to do when the id is unknown.

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