Skip to main content
Glama

Outil.io

Create invoice

create_invoice

Créer un brouillon de facture EUR, indépendant des factures du prestataire. Prix unitaires HT en euros, quantité jusqu’à 3 décimales, TVA en %. Calcul en centimes. Paramètres de facturation requis.

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": {
      "requestId": "<requestId>",
      "data": "<data>"
    },
    "name": "create_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYes
requestIdYesUUID stable pour les reprises de la même opération ; nouvel UUID si les données changent

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare it is a non-destructive, closed-world write; the description adds a genuinely new behavioral fact that the output is a DRAFT not an issued invoice, plus that amounts are computed in cents with EUR currency. It stops short of stating editability of the draft, idempotent behavior (covered only by the schema's requestId), or any auth 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?

Four short clauses, front-loaded with the resource and its distinguishing scope, then calculation rules. No filler or restatement of the title.

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

Completeness3/5

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

For a tool with a deeply nested schema (client, lines array, dates) and no output schema, the description covers the monetary/quantity semantics well but says nothing about the nested client payload, date fields, or the requestId idempotency contract. Adequate but visibly incomplete for this complexity.

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?

With only 50% schema description coverage, the description compensates by explaining that unitPrice is HT (tax-exclusive) in euros, quantity allows up to 3 decimals, and vatRate is a percentage — semantics that the raw schema types and bounds do not convey. It leaves the client object, dueDate/serviceDate, and operation enum unaddressed.

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?

States a specific verb and resource ('Créer un brouillon de facture EUR') and adds a scope qualifier ('indépendant des factures du prestataire') that separates it from the provider-invoice tooling. It does not name specific siblings such as create_invoice_credit or issue_invoice, so terminal differentiation still takes some inference.

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?

The word 'brouillon' (draft) implies this is the pre-issuance step rather than final invoicing, and 'indépendant des factures du prestataire' scopes it away from provider invoices. However, there is no explicit when-to-use statement, no mention of when to use issue_invoice instead, and no prerequisites or permission notes.

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.