Skip to main content
Glama

Explain a business rule

explain_rule
Read-onlyIdempotent

Explain an e-invoicing business rule by its id, such as BR-CO-15, BR-DE-1, PEPPOL-EN16931-R001 or a national CIUS rule: its message, level, the rule sets it belongs to, why invoices fail it and how to fix them. No sign-in or API key needed.

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": {
      "id": "<id>"
    },
    "name": "explain_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe rule id as the validator reports it, such as BR-CO-15.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's main added value is the auth note ('no sign-in or API key needed') and the disclosure of what the response contains. It says nothing about behavior for unknown/malformed ids, rate limits, or whether results are cached.

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 sentence plus a short auth clause, front-loaded with the verb and resource and then the concrete id examples. Every clause (examples, return contents, auth note) carries information the agent needs; no filler.

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

Completeness5/5

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

With no output schema, the description takes on the job of describing return values and does so explicitly (message, level, rule sets, failure explanation, remediation). For a single-parameter lookup with full annotation coverage, nothing essential is missing.

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?

The schema already documents the single id parameter at 100% coverage, so baseline is 3; the description adds real meaning by showing the accepted id families (BR-, PEPPOL-, national CIUS) that the schema's lone example does not suggest. This tells the agent the parameter is not limited to CEN rule ids.

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 verb (Explain) and resource (e-invoicing business rule) keyed by id, gives four concrete id formats (BR-CO-15, BR-DE-1, PEPPOL-EN16931-R001, national CIUS), and enumerates the returned content (message, level, rule sets, failure cause, fix). An agent can tell this apart from explain_error or get_validation without opening a 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 phrase 'by its id, such as ... as the validator reports it' establishes the usage context: call this when you already hold a rule id, presumably from a validation failure. It stops short of explicit when-not-to-use guidance or naming an alternative tool such as explain_error for error ids.

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