Skip to main content
Glama

explain_facturx_rule

Explique une règle normative Factur-X / EN 16931 / BR-FR-CTC ou PDF/A-3 et fournit un exemple XML correct.

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": {
      "code": "<code>"
    },
    "name": "explain_facturx_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesCode d'erreur (ex: BR-CO-15, BR-FR-04, PDFA3-FX-NS-INVALID).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does disclose the headline behavior: it returns an explanation plus a correct XML example. Beyond that it is silent on whether unknown or malformed codes are rejected, what language the explanation comes back in, and whether it is a pure static lookup versus something that hits a normative source. Useful but incomplete for a no-annotation 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?

A single well-formed sentence with the verb and deliverable front-loaded and no filler. It is appropriately sized for a one-parameter lookup tool; a brief clause on error-code origin would still have earned its place, which keeps it off a 5.

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 simple one-required-parameter read operation with no output schema, the description covers what the tool does and what it returns (explanation + sample XML), which is close to sufficient. The remaining gap is failure behavior for invalid codes and the response language, minor for this complexity level.

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 coverage is 100% and the schema already carries concrete example codes (BR-CO-15, BR-FR-04, PDFA3-FX-NS-INVALID), so the baseline of 3 applies. The description confirms that the code identifies a normative rule but adds no format constraints, prefix conventions, or tolerance rules beyond what the schema states.

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 names a specific verb ("Explique") and a specific resource (a normative rule from Factur-X / EN 16931 / BR-FR-CTC / PDF/A-3), and it even states the deliverable: a correct XML example. That is far more than a restatement of the name. It stops short of distinguishing itself from siblings such as validate_facturx or repair_facturx_envelope, so a 4 rather than a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the parameter being an "Code d'erreur" suggests this is the lookup an agent reaches for after a validation failure, but the description never says so. There is no explicit when-to-use, no exclusion, and no pointer to the sibling tools that might be the correct choice instead.

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