Skip to main content
Glama
Sign In

Dispolà

by ca.dispola
OverviewDiscussionsAdmin

Chercher des places libres

chercher_places
Read-onlyIdempotent

Cherche les places libres d'une ville, par catégorie, jour, moment et quartier, et au besoin par condition de santé ou par clientèle (commerces Dispolà Pro qui l'ont cochée). Rend l'établissement, le quartier, le service, l'heure, la durée, le prix et le lien pour réserver. Avec une catégorie, rend aussi sur_demande : des commerces sans réservation en ligne, avec des moments estimés à confirmer. / Finds open appointment spots in a city, by category, day, time of day and neighbourhood, optionally by health condition or clientele, with the booking link. With a category, also returns sur_demande: businesses without online booking, with estimated times to be confirmed by phone.

Input Schema

NameRequiredDescriptionDefault
latNoLatitude, avec lng : trie du plus proche au plus loin. / Latitude, with lng: sorts nearest first.
lngNoLongitude, avec lat. / Longitude, with lat.
jourNoaujourdhui, demain ou AAAA-MM-JJ (heure de Montréal). / today, tomorrow or YYYY-MM-DD.
villeYesLa ville, ou ailleurs : ailleurs au Québec, hors des villes du site (Trois-Rivières, Granby, Saguenay...) ; donne alors la ville de la personne dans quartier, ou lat et lng. / The city, or ailleurs: elsewhere in Quebec; then give the person's town in quartier, or lat and lng.
limiteNoNombre de places, 10 par défaut. / Max spots, default 10.
momentNoam : avant midi ; pm : de midi à 17 h ; soir : après 17 h. / morning, afternoon, evening.
quartierNoUn quartier, par exemple Plateau ou Limoilou : trie du plus proche au plus loin. / A neighbourhood: sorts nearest first.
categorieNoLa catégorie (voir categories_et_villes). / The category.
clienteleNoUne clientèle (femmes_enceintes, enfants, aines, mobilite_reduite...) : seulement les commerces Dispolà Pro qui l'ont cochée. Sans sur_demande. / A clientele: only Dispolà Pro businesses that checked it.
conditionNoUne condition de santé (maux_de_dos, stress, commotion...) : seulement les commerces Dispolà Pro qui se disent à l'aise avec elle. Pas un diagnostic : ce que le ou la pro dit connaître. Sans sur_demande. / A health condition: only Dispolà Pro businesses that checked it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / clientele
      Added value: +{
+  "description": "Une clientèle (femmes_enceintes, enfants, aines, mobilite_reduite...) : seulement les commerces Dispolà Pro qui l'ont cochée. Sans sur_demande. / A clientele: only Dispolà Pro businesses that checked it.",
+  "enum": [
+    "femmes_enceintes",
+    "bebes",
+    "enfants",
+    "ados",
+    "aines",
+    "couples",
+    "familles",
+    "lgbtq",
+    "autisme",
+    "diabete",
+    "deficience_intellectuelle",
+    "sourdes",
+    "mobilite_reduite"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / condition
      Added value: +{
+  "description": "Une condition de santé (maux_de_dos, stress, commotion...) : seulement les commerces Dispolà Pro qui se disent à l'aise avec elle. Pas un diagnostic : ce que le ou la pro dit connaître. Sans sur_demande. / A health condition: only Dispolà Pro businesses that checked it.",
+  "enum": [
+    "acouphenes",
+    "arthrite",
+    "arthrose",
+    "atm",
+    "blessures_sportives",
+    "bursite",
+    "cancer",
+    "canal_carpien",
+    "capsulite",
+    "circulation",
+    "commotion",
+    "coup_de_fouet",
+    "douleur_chronique",
+    "entorse",
+    "epicondylite",
+    "fasciite_plantaire",
+    "fatigue",
+    "hernie_discale",
+    "maux_de_cou",
+    "maux_de_dos",
+    "maux_de_tete",
+    "menopause",
+    "oedeme",
+    "plancher_pelvien",
+    "posture",
+    "inflammation",
+    "readaptation",
+    "sciatique",
+    "scoliose",
+    "sommeil",
+    "stress",
+    "tendinite",
+    "torticolis",
+    "digestif"
+  ],
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • changedInput schema / properties / ville / description
      Previous value: -"La ville. / The city."New value: +"La ville, ou ailleurs : ailleurs au Québec, hors des villes du site (Trois-Rivières, Granby, Saguenay...) ; donne alors la ville de la personne dans quartier, ou lat et lng. / The city, or ailleurs: elsewhere in Quebec; then give the person's town in quartier, or lat and lng."
    • changedInput schema / properties / ville / enum
      Previous value: -[
-  "montreal",
-  "quebec",
-  "sherbrooke",
-  "gatineau",
-  "rive-nord",
-  "rive-sud"
-]New value: +[
+  "montreal",
+  "quebec",
+  "sherbrooke",
+  "gatineau",
+  "rive-nord",
+  "rive-sud",
+  "ailleurs"
+]
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive safety, and the description adds genuinely new behavior: the exact result fields (établissement, quartier, service, heure, durée, prix, booking link) plus the conditional sur_demande block returned only when a category is supplied, with estimated times 'to be confirmed by phone'. It stops short of describing ordering guarantees or what an empty result means, so not 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?

Purpose and filter scope are front-loaded, and each sentence (return fields, then the sur_demande caveat) carries information. The full French/English duplication roughly doubles length, which is a deliberate bilingual choice rather than padding, but it does cost some density.

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

Completeness4/5

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

With 10 parameters, five enums and no output schema, the description does the important work of enumerating return fields and the conditional sur_demande payload, which the schema cannot convey. It leaves minor gaps around result ordering (beyond the 'nearest first' notes in the schema) and what happens when zero spots match.

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 coverage is 100%, so every parameter is already documented in the schema, including the enums, defaults and limites cap. The description adds only the cross-parameter rule that categorie triggers sur_demande while clientele/condition disable it, which duplicates what those parameter descriptions already say. Baseline 3 is right.

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 ('Cherche les places libres') plus the full filter scope (ville, catégorie, jour, moment, quartier, condition, clientèle) and enumerates the returned fields. An agent can distinguish it from the sibling lookup tools (categories_et_villes, proposer_limites, preparer_demande) 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 Guidelines3/5

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

Usage is implied rather than stated: the description notes that clientèle/condition narrow results to Dispolà Pro businesses and suppress sur_demande, and the category enum points to categories_et_villes for valid values. But it never explicitly says when to pick this tool over a sibling, nor any exclusion or precondition (e.g. whether it must follow proposer_limites or preparer_demande).

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

All Dispolà toolsInspect
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