Skip to main content
Glama

Rulepass e-invoicing

Example invoice input

example_invoice
Read-onlyIdempotent

Returns a complete, valid example input for create_einvoice (a Belgian domestic invoice at 21% VAT) to copy and adapt.

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": "example_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered. The description adds substantive context beyond that by disclosing the exact shape of the returned content (Belgian domestic, 21% VAT) and its fixed nature, though it does not say whether the example is guaranteed to pass validation against create_einvoice.

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?

A single sentence, front-loaded with the return value and followed by the qualifying scope and intended action. No filler.

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 zero-parameter, no-output-schema helper, the description covers what comes back and why. A small gap remains: it does not state that the returned object is directly consumable as the argument to create_einvoice, which is the key contract for this tool.

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 tool takes zero parameters and the schema is empty, so there is nothing for the description to disambiguate. Baseline 4 applies.

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 and resource ('Returns a complete, valid example input for create_einvoice') plus the concrete scope of the payload (Belgian domestic invoice at 21% VAT). It is immediately distinguishable from the sibling create_einvoice, which actually creates rather than exemplifies.

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?

'To copy and adapt' gives clear intent: fetch this before calling create_einvoice and modify the result. There is no explicit statement of when not to use it, e.g. that the example only fits Belgian domestic 21% VAT cases and is unsuitable as a template for other VAT rates or cross-border scenarios.

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.