Skip to main content
Glama

Synergieloc — French real estate & building CAD/BIM

search_tools

QUAND : avant tout, pour trouver l'outil Synergieloc qui répond au besoin (gestion locative, syndic, CAO/BIM, DXF/IFC/PDF, permis…). Renvoie noms et résumés, sans schéma. Ensuite : get_tool_schema puis 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": {
      "query": "<query>"
    },
    "name": "search_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesBesoin en mots-clés, ex. « révision loyer IRL »
limiteNo
categorieNoOptionnel : filtre (voir list_tool_categories)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the return shape ('renvoie noms et résumés, sans schéma'), which usefully warns the agent it must follow up with get_tool_schema, but it says nothing about relevance ranking, whether results are capped by the default limit of 10, or that the operation is a non-destructive read.

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

Conciseness5/5

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

Three short clauses, front-loaded with the 'QUAND :' cue, then the return shape, then the next step. Every sentence earns its place; nothing is padded.

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?

There is no output schema, and the description compensates by naming what is returned (names and summaries, not schemas) plus the follow-up tool chain. What remains uncovered is minor for a search tool: the meaning of limite and how results are ordered.

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 67%: query and categorie carry their own descriptions, while limite has only default/min/max bounds. The description reinforces the keyword semantics of query with domain examples ('gestion locative, syndic, CAO/BIM…') and implicitly points categorie at list_tool_categories, but adds nothing about numero limits or what the integer does.

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 and resource ('trouver l'outil Synergieloc'), gives the domain scope (gestion locative, syndic, CAO/BIM, DXF/IFC/PDF, permis) and explicitly says what comes back ('noms et résumés, sans schéma'). It positions itself as the entry point ('avant tout'), which separates it from get_tool_schema/execute_tool, but it never contrasts with the sibling list_tool_categories (browse vs. search), leaving one plausible confusion unresolved.

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?

Explicitly states when to call it ('QUAND : avant tout') and spells out the exact follow-up sequence: search_tools, then get_tool_schema, then execute_tool. The alternative path is named and the condition for taking it is clear, so the agent needs no inference to place this tool in the workflow.

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