Skip to main content
Glama

Invoice Parsing

invoice-parse
Read-only

Extract structured data from invoices and receipts. Returns the invoice number, dates, supplier and customer, currency, subtotal, tax, total and every line item. Use for an invoice or receipt given as a PDF or image URL. For any other document use documents with your own schema. Cost: 3 credits, charged only when a call succeeds.

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": {
      "document_url": "<document_url>"
    },
    "name": "invoice-parse"
  }
}

Input Schema

NameRequiredDescriptionDefault
document_urlYesURL to invoice PDF/image.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only, open-world, and non-destructive behavior, so the description's job is to add context — and it does, disclosing the cost model ("3 credits, charged only when a call succeeds") and the shape of the payload it returns. It stops short of mentioning input size limits or failure modes beyond billing, which keeps it from a 5.

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 sentences with no waste: purpose first, then return contents, then usage scope, then cost. Front-loads what the agent most needs and puts the sibling routing before the billing note.

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?

For a one-input tool with no output schema, the description carries the burden of describing returns and does so by naming each extracted field. Combined with the annotations and fully documented schema, an agent has everything needed to select and call it correctly.

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?

There is a single required parameter with 100% schema description coverage, so the schema already explains that `document_url` is a URL to an invoice PDF/image. The description's mention of PDFs and images merely echoes that, adding no new syntax or constraint detail — the baseline 3 for a one-param, fully documented schema.

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?

Names a specific verb and resource ("Extract structured data from invoices and receipts") and enumerates the returned fields, so the agent knows exactly what comes back. It also distinguishes itself from the `documents` sibling by scoping itself to invoices/receipts only.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use condition ("an invoice or receipt given as a PDF or image URL") and an explicit when-not with the named alternative ("For any other document use documents with your own schema"). Nothing is left to inference.

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.