ConformRadar

generate_legal_guarantee_box

Read-onlyIdempotent

Build the mandatory "legal guarantees" box for terms of sale of goods sold to consumers in France: the official text of the French Consumer Code template (annex to art. D. 211-2, model A), with the seller's details, as HTML and plain text. Valid for the sale of goods only (pets and digital content or services have other templates).

Args:
    seller_name: name of the seller who answers for the guarantees.
    seller_postal_address: postal address.
    seller_phone: phone number.
    seller_email: e-mail address or another digital contact.

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": {
      "seller_name": "<seller_name>",
      "seller_postal_address": "<seller_postal_address>",
      "seller_phone": "<seller_phone>",
      "seller_email": "<seller_email>"
    },
    "name": "generate_legal_guarantee_box"
  }
}

Input Schema

Name	Required	Description	Default
`seller_name`	Yes
`seller_email`	Yes
`seller_phone`	Yes
`seller_postal_address`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint=true and destructiveHint=false, so the safety/idempotency profile is provided structurally. The description adds output-format transparency (HTML and plain text) and the goods-only constraint, but says nothing about how the seller details are embedded or failure modes when out of scope.

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?

Front-loaded purpose sentence followed by the validity caveat, then a clean parameter list. Slightly verbose due to long legal reference, but every element earns its place.

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?

Covers purpose, scope limits, and all four parameters for a generation tool with no output schema. Sufficient for correct invocation; only minor gaps (exact output structure, out-of-scope behavior) remain.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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. It documents all four required parameters with clear intent (e.g., 'e-mail address or another digital contact'), compensating well for the empty schema. It could add format expectations (e.g., phone format) but is otherwise solid.

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 (Build) and a specific artifact (the mandatory legal guarantees box for French consumer terms of sale), and names the exact legal basis (annex to art. D. 211-2, model A). No sibling tool produces this artifact, so it is clearly distinguished.

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?

Explicitly scopes applicability: 'Valid for the sale of goods only (pets and digital content or services have other templates).' This tells the agent when NOT to use it, though it doesn't name the specific alternative tool/template to route to.

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

All ConformRadar tools Inspect

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

Need Help?