Skip to main content
Glama

Chercher une commune

callejear_search_communes
Read-onlyIdempotent

Trouver une commune et son code INSEE, étape préalable à la recherche d’une rue. Les homonymes se distinguent par leur département. Les noms sont ceux du catalogue local et peuvent être anciens.

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": "callejear_search_communes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
cursorNo

Output Schema

NameRequiredDescriptionDefault
errorNo
resultNo
statusYes
sourcesYes
limitationsYes
data_versionYes
responded_atYes
calculated_atYes
not_availableYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedOutput schema / properties / result / properties / next_cursor / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / result / properties / next_cursor / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / schema_version / const
      Previous value: -"1.0"New value: +"2.0"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description contributes genuinely new context by warning that names come from the local catalog and 'peuvent être anciens', which affects match expectations. It says nothing about result volume, pagination, or what happens when no commune matches, so it adds only partial value beyond the structured fields.

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?

Three short sentences, each doing distinct work: purpose and ordering first, then disambiguation, then a data-quality caveat. Front-loaded and free of filler. A slightly more explicit link to the street-search tool would have made it tighter still, but nothing is redundant.

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?

An output schema exists, so the INSEE code and commune fields need no explanation, and annotations cover the safety contract. What remains missing is pagination behavior for a tool that exposes limit and cursor, and any hint about empty-result handling. For a simple lookup the description is close to adequate but has a real gap around iterating results.

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% across three parameters, so the description carries the full burden. It only enriches the meaning of 'query' (catalog-sourced, possibly archaic names, homonyms split by département) and says nothing about 'limit' or 'cursor', leaving pagination semantics entirely undocumented. Two of three parameters get no semantic help anywhere in the definition.

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 states a specific verb+resource ('Trouver une commune et son code INSEE') and adds that it is 'étape préalable à la recherche d'une rue', which effectively positions it relative to the street-search sibling. It stops short of naming an alternative tool, but an agent can tell it apart from a street-search or coverage tool from the text alone.

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

Usage Guidelines4/5

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

Clear ordering guidance is given: this lookup comes before searching for a street, which tells the agent when to reach for it. It also notes that homonyms are distinguished by their département, hinting at the disambiguation workflow. There are no explicit exclusions or negative cases ('do not use when...'), so it does not reach the top band.

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