Skip to main content
Glama

TOISE — intelligence foncière

Comparer 2 à 10 zones de chalandise côte à côte

toise_comparer_zones
Read-onlyIdempotent

Quelle adresse choisir entre 2 et 10 emplacements : comparer leurs zones de chalandise côte à côte en UN seul appel (toutes les adresses dans zones). Chaque zone accepte les paramètres de toise_zone_chalandise. Ne pas appeler toise_zone_chalandise une fois par adresse.

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

Input Schema

NameRequiredDescriptionDefault
zonesYes2 à 10 zones à comparer.

Output Schema

NameRequiredDescriptionDefault
okYes
liensNoLiens vers la fiche TOISE et vers des services de…
quotaNoQuota du jour après cet appel : { fonction, limite…
zonesYesUne colonne par zone : habitants, âges, revenus…
ecartsYesÉcarts signalés entre zones, sans classement.
curseurNo
partielNotrue : une source n’a pas répondu, des champs manquent…
refusesYesZones non calculées…
sourcesYes
has_moreYesVrai si la liste a d’autres éléments : rappeler avec…
lecturesYes
warningsYesAvertissements (paramètres ignorés, données partielles).
quota_unitesNoUnités d’usage du jour : consommees_par_cet_appel…
champs_absentsNoDonnées absentes du résultat partiel.
sources_detailNo
limite_atteinteNoPrésent quand un quota, une limite d’offre ou une fonction…
paiement_requisNoPrésent quand le résultat complet est un achat à l’acte…

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuine behavioral context beyond them: the work is batched into a single call rather than fanned out, which matters for cost and rate limits. It does not discuss ordering of results or limits on response size, but the output schema exists to carry return-shape detail.

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, front-loaded with the user question, then the single-call mechanism, then the prohibition on looping the sibling tool. Nothing is redundant and the constraint is placed where an agent will read it before composing arguments.

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

Completeness5/5

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

For a one-parameter batch tool with full schema descriptions, rich annotations and an output schema, the description covers the decision context, the batching contract and the routing away from the sibling. Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so per-field meaning (km, minutes, mode, secteurs, ca_min, etc.) is already documented, which sets a baseline of 3. The description goes beyond that by telling the agent that each element of `zones` accepts the parameters of toise_zone_chalandise, a cross-tool contract the schema alone does not state.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('comparer leurs zones de chalandise côte à côte') plus an explicit scope ('entre 2 et 10 emplacements', 'en UN seul appel'). It also frames the decision the tool answers ('Quelle adresse choisir'), which lets an agent distinguish it from the single-zone sibling without opening the schema.

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?

It names the alternative tool explicitly and states the anti-pattern to avoid: 'Ne pas appeler toise_zone_chalandise une fois par adresse.' That is an unambiguous when-to-use-this-instead-of-that rule, and it also explains how to feed the batch ('toutes les adresses dans `zones`').

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