Skip to main content
Glama

Chercher une rue

callejear_search_streets
Read-onlyIdempotent

Recherche textuelle dans une seule commune, identifiée par son code INSEE. Résultats triés par nom, sans classement de qualité. Les liens sont issus du manifeste local, sans garantie de disponibilité actuelle.

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>",
      "city_id": "<city_id>"
    },
    "name": "callejear_search_streets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
cursorNo
city_idYes

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. Changed6 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"
      +]
    • removedOutput schema / properties / result / properties / streets / items / properties / iris_id / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / result / properties / streets / items / properties / iris_id / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / result / properties / streets / items / properties / point / anyOf
      Previous value: -[
      -  {
      -    "prefixItems": [
      -      {
      -        "maximum": 90,
      -        "minimum": -90,
      -        "type": "number"
      -      },
      -      {
      -        "maximum": 180,
      -        "minimum": -180,
      -        "type": "number"
      -      }
      -    ],
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": false,
      +    "maxItems": 2,
      +    "minItems": 2,
      +    "prefixItems": [
      +      {
      +        "maximum": 90,
      +        "minimum": -90,
      +        "type": "number"
      +      },
      +      {
      +        "maximum": 180,
      +        "minimum": -180,
      +        "type": "number"
      +      }
      +    ],
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / properties / schema_version / const
      Previous value: -"1.0"New value: +"2.0"
  2. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely non-derivable behavior: results are sorted by name with no relevance/quality ranking, and returned links come from a local manifest with no guarantee of current availability. The staleness caveat and the ordering guarantee are exactly the kind of context annotations cannot express.

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 sentences, no filler: scope first, then result ordering, then data provenance caveat. Every sentence adds information an agent would otherwise have to guess.

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 and annotations cover the safety profile, so return values and safety need no prose. However, for a paginated search tool with four undocumented parameters, the absence of any pagination/limit guidance leaves a real gap in what an agent needs to call it correctly.

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%, so the description carries the whole burden; it clarifies that the search text goes against a single commune and that city_id is an INSEE code (matching the schema pattern). It says nothing about limit or cursor, leaving pagination semantics undocumented in both schema and description, so compensation is only partial.

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 gives a specific verb and scope: a text search constrained to a single commune identified by its INSEE code, with results ordered by name. It is clear what the tool does, but it never names the resource (streets) explicitly nor distinguishes itself from siblings such as callejear_search_communes or callejear_compare_streets.

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?

The only usage constraint stated is the single-commune scope; there is no when-to-use guidance, no mention of when to prefer callejear_search_communes, callejear_compare_streets, or callejear_get_street_context, and no prerequisites. The agent must infer routing from tool names alone.

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