Skip to main content
Glama

Invoice Checker

controler_facture

Vérifie les montants, la date et les lignes d’une facture. Le taux de TVA est exprimé en pourcentage.

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": {
      "facture": "<facture>"
    },
    "name": "controler_facture"
  }
}

Input Schema

NameRequiredDescriptionDefault
factureYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It does not disclose whether the tool is read-only, what it returns on success or failure, whether validation errors are thrown or collected, or any side effects or permissions requirements.

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?

The description is two short sentences with no wasted wording, and the main purpose is front-loaded. The parameter note follows logically and does not obscure the primary function.

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

Completeness2/5

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

Given the complexity of the nested invoice object, the absence of annotations, and no output schema, the description is incomplete. It does not clarify what successful verification returns, how failures are reported, or which consistency rules are applied to amounts, dates and lines.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has low description coverage for a nested invoice object, and the description adds little beyond naming the checked categories. The note that 'Le taux de TVA est exprimé en pourcentage' duplicates the schema's own description of tauxTva, and there is no explanation of expected relationships among totalHT, totalTVA and totalTTC, currency handling, or line-item validation.

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 ('Vérifie') and resource ('facture'), and enumerates the checked aspects: montants, date and lignes. It is clear enough to identify the operation, though it does not define what the verification entails beyond those broad categories.

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

Usage Guidelines2/5

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

The description gives no explicit guidance on when to use this tool, when not to use it, or any prerequisites. The only implied usage is that it is for validating invoice data, which is not a substitute for actual usage guidance.

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