Skip to main content
Glama

Outil.io

Generate legal pages

generate_legal_pages

Créer ou mettre à jour les pages légales du site depuis la charte : mentions légales, politique de confidentialité RGPD (sous-traitants réels d’Outil), CGV (prestation de services ou vente) et cookies, puis les relier au pied de page de toutes les pages. Mentions publiées si la charte est complète ; les autres restent en brouillon needsReview jusqu’à relecture du client (reviewed + publish). toComplete liste les blancs à remplir.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "generate_legal_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindsNo
termsNo
publishNoPages à publier tout de suite. Défaut : mentions (factuelles), publiées seulement si aucune information n’y manque. Ne publier privacy/terms/cookies qu’après relecture par le client.
reviewedNoPages relues et validées par le client (retire needsReview).
analyticsNoLe site utilise des cookies de mesure d’audience ou publicitaires tiers
extraProcessorsNoOutils tiers ajoutés par le client (Google Analytics, Calendly, Mailchimp…)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses the real behavioral core: a draft/review state machine (needsReview until reviewed + publish), conditional auto-publishing, side effects on the footer of every page, and a toComplete list of remaining blanks. It does not warn about overwriting previously edited legal text on re-run, which is the main residual risk for a non-destructive-but-mutating tool.

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?

Three sentences, front-loaded with the create/update action, then the publishing rules, then the toComplete return hint. Dense but every clause carries information; the enumeration of the four page types is slightly long relative to the kinds enum in the schema.

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

Completeness3/5

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

For a 6-parameter tool with a nested terms object and no output schema, the description covers workflow and outcomes reasonably well, but leaves the 'charte' source undefined and says nothing about what happens to existing legal pages on a second invocation. Adequate, with a notable gap for a mutation tool.

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?

With 67% schema coverage, the schema already describes publish, reviewed, analytics and extraProcessors well; the description adds nuance about mentions being publishable only when the charte is complete and about CGV depending on services vs sales. However, analytics and extraProcessors receive no elaboration in the description, and 'charte' is used as an input source without explaining how it is supplied.

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?

The description states a specific verb pair and resource ('Créer ou mettre à jour les pages légales du site') and enumerates the exact artifacts produced: mentions légales, politique de confidentialité RGPD, CGV and cookies, plus footer linking. It stops short of distinguishing itself from the sibling list_legal_pages, so an agent must infer the read-vs-generate split from the names alone.

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?

It gives explicit operating conditions: factual mentions are published only if the charte contains no gaps, while privacy/terms/cookies stay in needsReview until the client validates via reviewed + publish. No sibling alternative is named and no precondition about when to re-run versus use batch_update_pages, which keeps it from a 5.

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.