Skip to main content
Glama
Sign In

Dispolà

by ca.dispola
OverviewDiscussionsAdmin

Lien d'alerte texto

lien_alerte_texto
Read-onlyIdempotent

Construit le lien du formulaire prérempli d'alerte texto quand aucune place ne convient. La personne l'ouvre, entre elle-même son cellulaire et consent aux textos ; l'outil ne soumet rien. / Builds a prefilled text alert form link; the person enters their own number and consents. The tool submits nothing.

Input Schema

NameRequiredDescriptionDefault
jourNoaujourdhui, demain ou AAAA-MM-JJ (heure de Montréal). / today, tomorrow or YYYY-MM-DD.
villeYesLa ville. / The city.
langueNoLangue du formulaire. / Form language.fr
momentNoam : avant midi ; pm : de midi à 17 h ; soir : après 17 h. / morning, afternoon, evening.
serviceNoLe code du service, par exemple ongles.gel (voir categories_et_villes). / Service code.
quartierNoLe quartier de la personne. / Their neighbourhood.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / service / enum
      Previous value: -[
-  "coiffure.coupe_femme",
-  "coiffure.coupe_homme",
-  "coiffure.coloration",
-  "coiffure.mise_en_plis",
-  "coiffure.barbe",
-  "ongles.gel",
-  "ongles.manucure",
-  "ongles.remplissage",
-  "ongles.pedicure",
-  "cils.classique",
-  "cils.hybride",
-  "cils.volume",
-  "cils.remplissage",
-  "cils.rehaussement",
-  "sourcils.restructuration",
-  "sourcils.teinture",
-  "sourcils.laminage",
-  "sourcils.fil",
-  "esthetique.soin_visage",
-  "esthetique.cire",
-  "esthetique.bresilienne",
-  "massotherapie.suedois",
-  "massotherapie.therapeutique",
-  "massotherapie.tissus_profonds",
-  "massotherapie.prenatal",
-  "massotherapie.sportif",
-  "massotherapie.drainage_lymphatique",
-  "tatouage.flash",
-  "tatouage.petit",
-  "tatouage.retouche",
-  "physiotherapie.evaluation",
-  "physiotherapie.traitement",
-  "osteopathie.traitement",
-  "kinesiologie.seance",
-  "therapie_sport.traitement",
-  "chiropratique.traitement",
-  "acupuncture.seance"
-]New value: +[
+  "coiffure.coupe_femme",
+  "coiffure.coupe_homme",
+  "coiffure.coloration",
+  "coiffure.mise_en_plis",
+  "coiffure.barbe",
+  "ongles.gel",
+  "ongles.manucure",
+  "ongles.remplissage",
+  "ongles.pedicure",
+  "cils.classique",
+  "cils.hybride",
+  "cils.volume",
+  "cils.remplissage",
+  "cils.rehaussement",
+  "sourcils.restructuration",
+  "sourcils.teinture",
+  "sourcils.laminage",
+  "sourcils.fil",
+  "esthetique.soin_visage",
+  "esthetique.cire",
+  "esthetique.bresilienne",
+  "massotherapie.suedois",
+  "massotherapie.therapeutique",
+  "massotherapie.tissus_profonds",
+  "massotherapie.prenatal",
+  "massotherapie.sportif",
+  "massotherapie.drainage_lymphatique",
+  "massotherapie.orthotherapie",
+  "massotherapie.kinesitherapie",
+  "tatouage.flash",
+  "tatouage.petit",
+  "tatouage.retouche",
+  "physiotherapie.evaluation",
+  "physiotherapie.traitement",
+  "osteopathie.traitement",
+  "kinesiologie.seance",
+  "kinesiologie.evaluation",
+  "kinesiologie.entrainement",
+  "therapie_sport.traitement",
+  "chiropratique.traitement",
+  "acupuncture.seance"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / service / enum
      Previous value: -[
-  "coiffure.coupe_femme",
-  "coiffure.coupe_homme",
-  "coiffure.coloration",
-  "coiffure.mise_en_plis",
-  "coiffure.barbe",
-  "ongles.gel",
-  "ongles.manucure",
-  "ongles.remplissage",
-  "ongles.pedicure",
-  "cils.classique",
-  "cils.hybride",
-  "cils.volume",
-  "cils.remplissage",
-  "cils.rehaussement",
-  "sourcils.restructuration",
-  "sourcils.teinture",
-  "sourcils.laminage",
-  "sourcils.fil",
-  "esthetique.soin_visage",
-  "esthetique.cire",
-  "esthetique.bresilienne",
-  "massotherapie.suedois",
-  "massotherapie.therapeutique",
-  "massotherapie.tissus_profonds",
-  "massotherapie.prenatal",
-  "tatouage.flash",
-  "tatouage.petit",
-  "tatouage.retouche",
-  "physiotherapie.evaluation",
-  "physiotherapie.traitement",
-  "osteopathie.traitement",
-  "kinesiologie.seance",
-  "therapie_sport.traitement",
-  "chiropratique.traitement",
-  "acupuncture.seance"
-]New value: +[
+  "coiffure.coupe_femme",
+  "coiffure.coupe_homme",
+  "coiffure.coloration",
+  "coiffure.mise_en_plis",
+  "coiffure.barbe",
+  "ongles.gel",
+  "ongles.manucure",
+  "ongles.remplissage",
+  "ongles.pedicure",
+  "cils.classique",
+  "cils.hybride",
+  "cils.volume",
+  "cils.remplissage",
+  "cils.rehaussement",
+  "sourcils.restructuration",
+  "sourcils.teinture",
+  "sourcils.laminage",
+  "sourcils.fil",
+  "esthetique.soin_visage",
+  "esthetique.cire",
+  "esthetique.bresilienne",
+  "massotherapie.suedois",
+  "massotherapie.therapeutique",
+  "massotherapie.tissus_profonds",
+  "massotherapie.prenatal",
+  "massotherapie.sportif",
+  "massotherapie.drainage_lymphatique",
+  "tatouage.flash",
+  "tatouage.petit",
+  "tatouage.retouche",
+  "physiotherapie.evaluation",
+  "physiotherapie.traitement",
+  "osteopathie.traitement",
+  "kinesiologie.seance",
+  "therapie_sport.traitement",
+  "chiropratique.traitement",
+  "acupuncture.seance"
+]
  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 declare readOnlyHint/idempotentHint/destructiveHint=false, so the safety profile is covered; the description adds the genuinely useful behavioral fact that the end user enters their own number, gives consent, and 'l'outil ne soumet rien' — an important boundary no annotation conveys. No mention of link expiry or whether the URL is returned vs. displayed, but the key non-submission caveat is stated.

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 short sentences per language, with the purpose front-loaded and the non-submission caveat as the follow-up. The bilingual duplication adds length but is a deliberate mirror, not padding.

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?

For a read-only link builder with a fully documented schema and no output schema, the description covers purpose, trigger condition, and the user-consent boundary. Only the shape of the result (a URL string) and any link validity window are left implicit.

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% and 4 of 6 parameters carry enums with inline descriptions, so the schema does the heavy lifting. The description adds no parameter-level meaning beyond what the schema documents, giving the baseline 3.

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?

States a specific verb and resource ('Construit le lien du formulaire prérempli d'alerte texto') plus the fallback condition 'quand aucune place ne convient', which implicitly separates it from chercher_places and preparer_demande. It never names a sibling tool outright, so the differentiation is inferential rather than explicit.

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?

'quand aucune place ne convient' gives a clear trigger condition for when to call this instead of the booking/search tools. It stops short of stating what to do first (e.g. only after chercher_places returns nothing) or when not to use it.

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