DoubleData MCP

Download invoice PDF

download_invoice

Idempotent

Saves an invoice PDF to the local export directory using its invoice ID and returns the file path.

Instructions

Save an invoice PDF into the local export directory and return the file path.

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": {
      "invoice_id": "<invoice_id>"
    },
    "name": "download_invoice"
  }
}

Input Schema

Name	Required	Description	Default
`path`	No	Relative file path inside the export directory. Defaults to invoices/<number>.pdf.
`invoice_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnly=false, openWorld=true, idempotentHint=true and destructiveHint=false, so safety and repeatability are covered. The description adds the meaningful facts that output lands in the local export directory and that a file path is returned (useful since there is no output schema), but it says nothing about overwrite behavior on an existing path, permission/auth requirements, or failures for a missing invoice.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the action and the destination, with no filler. Its brevity is appropriate, though the space saved could have been used for the missing usage and return-failure detail.

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?

The description correctly states the return value, which matters because no output schema exists, and identifies the write target directory. For a file-writing tool it remains incomplete on overwrite semantics, error cases, and the undocumented invoice_id parameter, so it is adequate but with clear gaps.

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 description adds no meaning for either parameter. 'path' is documented in the schema, but 'invoice_id' has only a regex pattern and no prose anywhere, and schema coverage is 50%, so the description should have compensated for that gap and does not.

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?

Specific verb ('Save') plus resource ('invoice PDF') plus destination ('local export directory'), which is clear on its own. It does not distinguish itself from siblings like get_invoice (fetch data) or download_all_invoices (bulk), so an agent can't tell from this text why this single-invoice variant exists rather than the others.

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?

No when-to-use or when-not-to-use guidance and no reference to the obvious alternatives (download_all_invoices for bulk, get_invoice for metadata). The agent must infer selection rules entirely from sibling names, which the definition never mentions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.