Skip to main content
Glama

Lire la fiche d’un professionnel

fiche_pro
Read-onlyIdempotent

À utiliser quand l’utilisateur veut en savoir plus sur un professionnel précis ou le contacter. Rend ses coordonnées, ses horaires de la semaine, ses prestations et les prix publiés, ses équipements, ses photos, comment prendre rendez-vous, et pour un contrôle technique ses tarifs avec leur source. Exemple : slug=gmr-auto.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "gmr-auto"
    },
    "name": "fiche_pro"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesLe champ « slug » rendu par chercher_pros, ou l’URL de la fiche.

Output Schema

NameRequiredDescriptionDefault
nomNo
urlNoLa fiche bocaross.fr du professionnel.
slugNo
photoNo
metierNo
photosNo
adresseNo
communeNo
metiersNo
nb_avisNo
accrocheNo
horairesNo
site_webNo
ouvertureNo
telephoneNo
specialiteNo
code_postalNo
descriptionNo
distance_kmNo
equipementsNo
note_googleNo
prestationsNo
rendez_vousNo
prix_publiesNo
certifie_bocarossNoLe professionnel gère sa page sur BocaRoss ; il passe devant les autres sur les listes où il figure.
ouvert_maintenantNo
gestes_commerciauxNo
horaires_aujourdhuiNo
se_deplace_jusqu_a_kmNo
tarifs_controle_techniqueNoPour un centre de contrôle technique : ses tarifs déclarés à la DGCCRF (prix.conso.gouv.fr), sinon ceux affichés par son réseau, avec la source et la date. À confirmer auprès du centre.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "slug": "gmr-auto"
      +  }
      +]
    • changedInput schema / properties / slug / description
      Previous value: -"L’identifiant de la fiche, ex. « gmr-auto », ou son URL complète."New value: +"Le champ « slug » rendu par chercher_pros, ou l’URL de la fiche."
    • addedOutput schema / properties / ouverture
      Added value: +{
      +  "properties": {
      +    "etat": {
      +      "enum": [
      +        "ouvert",
      +        "ferme_bientot",
      +        "ferme"
      +      ],
      +      "type": "string"
      +    },
      +    "texte": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / tarifs_controle_technique
      Added value: +{
      +  "description": "Pour un centre de contrôle technique : ses tarifs déclarés à la DGCCRF (prix.conso.gouv.fr), sinon ceux affichés par son réseau, avec la source et la date. À confirmer auprès du centre.",
      +  "properties": {
      +    "a_partir_de": {
      +      "type": "boolean"
      +    },
      +    "contre_visite": {
      +      "properties": {
      +        "max": {
      +          "type": "number"
      +        },
      +        "min": {
      +          "type": "number"
      +        }
      +      },
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "date": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "prix": {
      +      "items": {
      +        "properties": {
      +          "energies": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "prix": {
      +            "type": "number"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "source": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A3.9/5.0
Behavior3/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=false, so the safety profile is fully covered and the description does not contradict it. The description adds content scope (contact details, published prices, booking flow, price sources for contrôle technique) but says nothing about failure behavior for an unknown slug or about rate limits. Much of the returned-field enumeration overlaps with the existing output schema.

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?

Usage guidance is front-loaded before the payload enumeration, and the example is appended compactly at the end. The middle clause listing every returned field is long but each item is substantive; no filler or repetition of the title.

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 one-parameter read tool with rich annotations and an output schema, the description covers when to call it and what kind of data comes back, which is sufficient. The only material gap is the absence of any note on what happens when the slug is invalid or not found.

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?

Single parameter with 100% schema description coverage; the schema already explains that slug comes from chercher_pros or is the fiche URL. The description only contributes an example value (slug=gmr-auto), which adds no new semantics. Baseline 3 applies when the schema does the explanatory work.

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 concrete verb and resource ('Lire la fiche d'un professionnel') plus scope ('un professionnel précis'), and enumerates the exact payload (coordonnées, horaires, prestations, prix, équipements, photos, prise de rendez-vous). This clearly separates it from the search sibling chercher_pros, which returns slugs rather than full records.

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?

'À utiliser quand l'utilisateur veut en savoir plus sur un professionnel précis ou le contacter' gives a clear triggering condition tied to a single known professional. It stops short of an explicit when-not clause or naming chercher_pros as the alternative for the discovery case.

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