Skip to main content
Glama

TOISE — intelligence foncière

Images de rue ouvertes autour d’une adresse

toise_imagerie_rue
Read-onlyIdempotent

Quelle est la rue autour d'une adresse : images de rue sous licence ouverte (Panoramax), avec date, distance et auteur. Couverture inégale ; une image proche n'est pas forcément la façade.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "toise_imagerie_rue"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNo
lonNo
limiteNo
adresseNo
joindreNoNombre d’images dont les PIXELS sont joints…
rayon_mNo

Output Schema

NameRequiredDescriptionDefault
liensNoLiens vers la fiche TOISE et vers des services de…
quotaNoQuota du jour après cet appel : { fonction, limite…
centreYes{ lat, lon, adresse_retenue }.
imagesYes
partielNotrue : une source n’a pas répondu, des champs manquent…
rayon_mYes
sourcesYes
warningsYes
candidatesYesNombre d’images trouvées dans le rayon avant sélection.
vide_motifNo
quota_unitesNoUnités d’usage du jour : consommees_par_cet_appel…
champs_absentsNoDonnées absentes du résultat partiel.
images_jointesNoNombre d’images dont les pixels sont joints à cette réponse…
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. Changed1 schema field changed
    • changedInput schema / properties / joindre / description
      Previous value: -"Nombre d’images dont les PIXELS sont joints à…"New value: +"Nombre d’images dont les PIXELS sont joints…"
  2. Changed1 schema field changed
    • changedInput schema / properties / joindre / description
      Previous value: -"Nombre d’images dont les PIXELS sont joints à la…"New value: +"Nombre d’images dont les PIXELS sont joints à…"
  3. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open world), so the description's job is to add context — and it does: it discloses uneven coverage ('Couverture inégale') and warns that proximity of an image does not imply it shows the subject façade, which directly affects result interpretation. It stops short of describing result volume, ordering across the spatial query, or why only a few images carry pixels.

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 compact sentences with no filler; the source and returned fields are front-loaded and the caveat follows. The opening interrogative construction is slightly indirect for a tool description but costs almost nothing.

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?

Return values needn't be explained since an output schema exists, and the behavioral caveats are good. But for a six-parameter, zero-required spatial query at 17% schema coverage, the agent is left without guidance on which locator form to supply or how the radius and image-count limits interact, which is a material gap.

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?

With six parameters, none required, and only 17% schema description coverage, the description carries most of the burden and provides none: it never explains whether 'adresse' and 'lat'/'lon' are interchangeable or mutually exclusive, what 'limite' caps, or the unit/default of 'rayon_m'. 'joindre' is the only documented parameter, and that documentation lives in the schema, not the description.

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 names a specific resource and source ('images de rue sous licence ouverte (Panoramax)') and states what the agent gets back ('avec date, distance et auteur'). It is clearly an imagery lookup rather than a cadastral or DVF tool, though it never names or contrasts any sibling tool.

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?

Usage is implied by the framing ('Quelle est la rue autour d'une adresse') and one caution is given ('une image proche n'est pas forcément la façade'), which tells the agent how to interpret results. There is no explicit when-to-use vs. when-not guidance and no routing to any alternative tool for other spatial needs.

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