smartbill-mcp

List invoices issued from an estimate

get_estimate_invoices

Read-only

Verify if a proforma estimate has been invoiced and fetch the resulting invoices to prevent duplicate billing.

Instructions

Check whether a proforma has already been invoiced, and which invoices came out of it. Read-only.

Call this before create_invoice_from_estimate to avoid double-invoicing the same proforma, and to answer questions like 'did we ever bill that quote?'. An empty result means the proforma is still open.

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": {
      "number": "<number>"
    },
    "name": "get_estimate_invoices"
  }
}

Input Schema

Name	Required	Description
`number`	Yes	Estimate number, without the series prefix.
`seriesName`	No	Estimate series. Falls back to the configured default.
`companyVatCode`	No	Issuing company CIF. Falls back to SMARTBILL_VAT_CODE.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 29, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces that it is read-only. It adds context about checking invoices, but no additional behavioral traits beyond what annotations convey.

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?

Only three sentences, front-loaded with purpose and usage. No unnecessary information.

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?

Given no output schema, the description explains what an empty result means and implies the result is a list of invoices. Adequate for a read-only list tool.

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 100%, so parameters are fully described in the schema. The description does not add further details about parameters, so baseline 3 is appropriate.

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?

The description clearly states the purpose: 'Check whether a proforma has already been invoiced, and which invoices came out of it.' It uses specific verbs and resources, and distinguishes from sibling tools like create_invoice_from_estimate.

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?

Provides explicit guidance: 'Call this before create_invoice_from_estimate to avoid double-invoicing' and answers specific questions. Tells what an empty result means.

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