Skip to main content
Glama

Lexou · droit français

Fiches pratiques Service-Public

fiche_service_public
Read-onlyIdempotent

Fiches officielles de Service-Public.fr (démarches, droits, formulaires CERFA, téléservices) cherchées par mots-clés dans la copie tenue par Lexou, avec la date de mise à jour et le lien officiel. Pas pour le texte d'un article de loi.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "recherche": "<recherche>"
    },
    "name": "fiche_service_public"
  }
}

Input Schema

NameRequiredDescriptionDefault
rechercheYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, closed-world, idempotent and non-destructive, so safety is covered. The description does add real context beyond them: the search runs against 'la copie tenue par Lexou' rather than the live site, and results carry an update date and official link. It does not say anything about result volume, ranking or freshness limits of that copy.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense sentence: resource and scope first, then retrieval mechanism, then output metadata, then the exclusion. Every clause carries information and nothing is repeated from the title or schema.

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-only search with no output schema and full annotation coverage, this is nearly sufficient: it names the data source and the salient return fields. Minor gaps remain around result count, ordering, and whether a miss returns an empty set or an error.

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 0%, so the description must carry the burden, and it only partially does: 'cherchées par mots-clés' tells the agent the single parameter is a free-text keyword query, but says nothing about multi-word behavior, accents, or the 2-200 character constraint enforced by the schema.

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 resource (fiches officielles de Service-Public.fr), the covered content (démarches, droits, formulaires CERFA, téléservices), the retrieval method (cherchées par mots-clés), and explicitly excludes one adjacent resource (le texte d'un article de loi). An agent can distinguish this from lire_article_de_loi 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?

The closing exclusion ('Pas pour le texte d'un article de loi') gives a clear negative condition that routes to a sibling category. It lacks an explicit positive trigger (e.g. 'use for administrative procedure questions') and never names the alternative tool, so the agent must infer the when-to-use half.

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