Skip to main content
Glama

Synergieloc — French real estate & building CAD/BIM

execute_tool

QUAND : pour exécuter un outil Synergieloc par son nom exact, avec les arguments de son schéma. Mêmes règles que /mcp : clé API (Authorization: Bearer slk_…) et carte enregistrée pour les outils payants.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
argumentsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

No annotations exist, so the description carries full burden. It does add real context the schema cannot: the API key requirement (Authorization: Bearer slk_…) and that paid tools require a registered card. It omits that side effects depend entirely on the dispatched tool, how errors are surfaced, and how the callee's result is returned — significant for a proxy that can trigger destructive operations.

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?

Two tight sentences, front-loaded with an explicit "QUAND :" marker, with no filler. The brevity borders on under-specification rather than excess, so nothing needs cutting.

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?

For a meta-dispatch tool with a free-form nested arguments object, no output schema and no annotations, the definition leaves critical gaps: no discovery workflow for resolving the exact tool name or its argument shape, and no indication of what the call returns or how the target tool's failures propagate.

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 0% and "arguments" is an untyped nested object with no properties, so the description must compensate. It does clarify that name is the exact tool name and that arguments must match the target tool's schema, which is genuine added meaning, but it doesn't say where that schema comes from or whether arguments are passed through verbatim.

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?

"Pour exécuter un outil Synergieloc par son nom exact, avec les arguments de son schéma" gives a specific verb (execute) and resource (a Synergieloc tool) plus the dispatch contract. It implicitly separates this from discovery siblings (search_tools, get_tool_schema), though it never names them, so differentiation is inferred rather than stated.

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?

The "QUAND :" prefix signals intended usage explicitly, which is more than most definitions offer. However, it only covers the positive case and never says when not to use it, nor does it point the agent to get_tool_schema/search_tools when the exact name or argument shape 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