Skip to main content
Glama

Outil.io

Download invoice PDF

download_invoice_pdf
Read-only

Télécharger le PDF figé d’une facture / d’un avoir ou un aperçu marqué BROUILLON. Renvoie filename, mime et data base64.

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

Input Schema

NameRequiredDescriptionDefault
idYes

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 already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: the PDF is 'figé' (frozen/final) or a DRAFT-watermarked preview, and the response carries filename, mime, and base64 data — details absent from any structured field since there is no output schema.

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?

Two short sentences with no filler: the action and its variants come first, the return shape second. Nothing is redundant or padded.

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 one-parameter read tool with no output schema, the description covers the return payload (filename, mime, base64) and the draft-vs-final distinction, which is the key ambiguity. The remaining gap is the meaning and validity conditions of the id argument.

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 description coverage is 0% and the single parameter is just 'id' (uuid) with no documentation. The description partially compensates by indicating the id can designate either an invoice or a credit note, but it does not state the format, nor what happens if the id refers to a non-issued or deleted record.

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: download the frozen PDF of an invoice or credit note, or a preview marked DRAFT. That distinguishes the output variants clearly, though it does not name a sibling or explain how it differs from export_catalog_pdf or download_teaching_file.

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?

Implies usage by saying the same call serves invoices, credit notes, and draft previews, which is useful context. However, it never states when to prefer this over a related export tool, nor any precondition such as the invoice needing to be issued before a frozen PDF exists.

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.