Skip to main content
Glama

get_tool

Détails d'un outil du catalogue.

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

Input Schema

NameRequiredDescriptionDefault
tool_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it adds nothing: no statement that this is a read-only lookup, no behavior on unknown tool_id, no error semantics, no hint at the shape of the returned details. It effectively restates the tool name.

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

Conciseness3/5

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

A single short sentence with no wasted wording, which is efficient, but the brevity reflects under-specification rather than tight editing. There is no front-loaded statement of what the agent gets back.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one required string parameter, no output schema), so requirements are modest, but the description never says what 'details' comprise, which is the main thing an agent needs when deciding to call it. With no annotations and no output schema, this gap is not covered elsewhere.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single tool_id parameter, so the description must compensate and does not. It never clarifies whether tool_id is a name, slug, UUID, or numeric identifier, leaving the agent to guess the expected format.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Détails d'un outil du catalogue" names the resource (a catalog tool) and vaguely the operation (retrieve details), so an agent can tell it fetches information rather than buying. But "détails" is generic and does not say what details are returned or how this differs from search_tools, which also operates on the catalog.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance at all. The siblings search_tools and find_and_buy are natural alternatives for catalog lookups, but the description gives no condition distinguishing 'I need a specific known tool's details' from 'I need to search'.

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