Mission Museaux

Trouver de l'aide près d'un lieu / Find local help

trouver_aide_locale

Read-onlyIdempotent

Find local help near a French town, postcode or listing: town hall (phone, hours, pound), nearest vets, shelters and pounds within 50 km, neutering aid. Use it after a pet is lost or found. Returns up to 10 places with distance, phone, hours, source; open data, call first. Accepts French or English; replies in French, or English with langue "en".

Input Schema

Name	Required	Description	Default
`besoin`	No	What is needed: tous (all, default), veterinaire (vets), refuge (shelters), fourriere (pound), mairie (town hall) or sterilisation (neutering aid for stray cats).	tous
`langue`	No	Response language: "fr" (French, default) or "en" (English). A request written in English is answered in English even without it.	fr
`annonce`	No	Listing id or url from chercher_annonces or voir_annonce (string), e.g. a 36-character UUID, instead of commune: searches around the centre of its town, never its exact spot.
`commune`	No	French town name or 5-digit postcode (string, 2 to 80 characters), e.g. "Nemours" or "77140". Searches around the town centre. France only; give commune or annonce.
`rayon_km`	No	Search radius in km around the town centre (number, 1 to 50, default 50). Shelters and pounds are listed within 10, then 25, then 50 km.

Output Schema

Name	Required	Description
`liens`	Yes	Neutering aid organisations, the OpenStreetMap editor and the data sources page.
`lieux`	Yes	Up to 10 places: the town hall first, then the closest of each kind. No coordinates.
`besoin`	Yes	The need searched for, as understood.
`centre`	Yes	The town centre that distances are measured from; null when the town is not covered.
`donnees`	Yes	Open data: OpenStreetMap (ODbL), Insee Sirene and Service-Public.
`rayon_km`	Yes	The radius used, in km (50 at most).
`demarches`	Yes	What to do, in plain steps (town hall and pound, neutering, call first).
`indisponible`	No	Present when the list of places is not available yet.
`mises_en_garde`	Yes	Warnings to pass on: open data that may be out of date, distances as the crow flies, places independent of Mission Museaux, no medical advice.
`lieu_non_couvert`	No	Present when the town given is abroad or not found: Mission Museaux covers France.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 15, 2026

addedOutput schema / properties / lieux / items / properties / lien_google_maps

Added value: +{
+  "description": "A Google Maps search for the place (name and town only), for the person to check phone, hours and reviews before calling; null for a town hall or State services, whose details come from the official directory.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / properties / lieux / items / required

Previous value: -[
-  "type",
-  "nom",
-  "commune",
-  "distance_km",
-  "telephone",
-  "horaires",
-  "horaires_lisibles",
-  "site",
-  "source",
-  "date_source",
-  "lien_osm"
-]New value: +[
+  "type",
+  "nom",
+  "commune",
+  "distance_km",
+  "telephone",
+  "horaires",
+  "horaires_lisibles",
+  "site",
+  "source",
+  "date_source",
+  "lien_osm",
+  "lien_google_maps"
+]

AddedOct 15, 2026

TDQS

A4.2/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, closed-world), but the description adds real value beyond them: a hard 10-result cap, the returned fields (distance, phone, hours, source), open-data provenance, the "call first" staleness warning, and language behavior. No auth, rate-limit, or error behavior is described, which keeps this short of a 5.

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 dense sentences that front-load the purpose, then usage and return/contract details. Slightly wasteful where it re-lists the enum values ("town hall (phone, hours, pound), nearest vets, shelters and pounds") that the schema already defines.

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 5-parameter, no-required-arg search tool with a full output schema and complete annotation coverage, the description supplies everything an agent still needs: when to call it, result cap, distance tiers, provenance caveat, and language handling. Return-value details are covered by the output schema, so nothing material is missing.

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 100%, so the schema already documents besoin, langue, commune, annonce and rayon_km thoroughly. The description mostly restates the enum categories and the French/English reply rule, adding little syntax or semantics the schema lacks (the 10/25/50 km tiering and 'never its exact spot' already live in the schema descriptions). Baseline 3 is correct.

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?

States a specific verb and resource (find local help near a French town/postcode/listing) and enumerates the exact result categories: town hall, vets, shelters, pounds, neutering aid. An agent can tell this apart from the sibling search tools (chercher_annonces, chercher_adoptions) without opening any schema.

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?

Gives a clear triggering context ("Use it after a pet is lost or found") and a practical caveat ("open data, call first"). It does not name which sibling to pick instead when the agent actually wants listings or adoption results, so the routing guidance is only partial.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Mission Museaux tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?