Skip to main content
Glama

Synergieloc — French real estate & building CAD/BIM

get_tool_schema

QUAND : après search_tools, pour lire le schéma d'entrée exact (1 à 5 outils) avant execute_tool.

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": {
      "names": "<names>"
    },
    "name": "get_tool_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It implies a read-only lookup and states the batch limit (1 to 5 tools), but says nothing about error behavior for unknown tool names, whether schemas are returned as structured objects or text, or what happens with partial matches.

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?

A single front-loaded sentence with a 'QUAND' tag that puts the trigger condition first. Zero filler, though the run-on structure merges trigger, action, and scope into one clause rather than separating them.

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

Completeness3/5

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

This is a simple one-parameter read tool, and the sequencing guidance is complete. However, the tool's entire value is the returned schema and there is no output schema, so the description should say more about what comes back (full JSON schema, per-tool errors, ordering) than it does.

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 0% for the single 'names' array parameter. The description compensates by stating the 1-to-5 cardinality and making clear the elements are tool names, which covers the minItems/maxItems constraint. It does not clarify name format (exact identifiers vs. partial) or whether an invalid entry fails the whole batch.

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 (read/lire) and resource (the exact input schema) plus scope (1 to 5 tools). An agent can distinguish it from execute_tool and search_tools without opening any schema, though the phrasing is compressed into a single tagged clause.

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

Usage Guidelines5/5

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

Gives an explicit workflow position: call it after search_tools and before execute_tool. This names both the prerequisite and the follow-up action, so the agent knows exactly when to invoke it and what it feeds into.

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