QuoteBill

Draft a quotation or invoice

build_document

Read-onlyIdempotent

Builds a complete quotation or invoice from line items, optionally starting from a template, and totals it. Returns a url that opens this document, filled in, on QuoteBill; nothing is saved to any account. Give them that url exactly as returned. When the document is in a language other than the one the person is writing to you in, pass that one as interfaceLanguage, so the page opens in their language.

Input Schema

TableJSON Schema

Name	Required	Description
`to`	No	Who the document is for.
`from`	No	Who is issuing the document.
`notes`	No	Notes shown on the document.
`terms`	No	Payment or acceptance terms.
`region`	No	Canadian province or territory code (for example QC, ON). Only accepted when country is CA.
`country`	Yes	Two-letter ISO country code of the place of supply, for example KR, JP, DE, GB.
`docType`	No	Defaults to the template's type, or quotation.
`dueDate`	No	Date written as YYYY-MM-DD that an invoice is payable by.
`taxRate`	No	Tax rate as a percentage, for example 10 for 10%. Overrides the published rate. Use it where the country has no single rate, such as the United States.
`language`	No	Language the document is written in — its headings, labels and dates — usually the customer's. Any of the 33 languages QuoteBill is written in, as a two-letter code such as en, ko, ja, zh, de, fr, es, ar or th. When left out: the template's own language, else interfaceLanguage, else en.
`issueDate`	No	Date written as YYYY-MM-DD. Defaults to today.
`lineItems`	Yes	Line items. A row with type "header" is a section heading and is not charged.
`validUntil`	No	Date written as YYYY-MM-DD that a quotation is good until.
`templateSlug`	No	Optional template to take the layout from.
`documentNumber`	No	Your reference for this document.
`interfaceLanguage`	No	Language the person reads QuoteBill in: the page the url opens is in this language. Usually the language they are writing to you in. Any of the 33 languages QuoteBill is written in, as a two-letter code such as en, ko, ja, zh, de, fr, es, ar or th. When left out: language, else en.

Output Schema

TableJSON Schema

Name	Required	Description
`tax`	Yes
`url`	Yes	Opens this document, filled in, on QuoteBill. The part after # is the document itself and never leaves the person's browser; pass the url on whole.
`next`	Yes	What to tell the person next.
`totals`	Yes
`document`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 25, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description reinforces this with "nothing is saved to any account." It also adds useful behavior beyond annotations: the tool returns a URL, the agent should "Give them that url exactly as returned," and interfaceLanguage controls the page's language.

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?

The description is compact and front-loaded: the first sentence states the core action, the second explains the return value and side-effect-free behavior, the third gives a direct instruction, and the fourth adds a parameter-use rule. Every sentence earns its place with no filler.

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 complex 16-parameter tool with nested objects and an output schema, the description is complete: it covers what is built, what is returned, that nothing persists, how to handle the returned URL, and how to handle language mismatches. The schema and output schema cover the remaining parameter details.

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?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful parameter-level guidance by explaining when to set interfaceLanguage: when the document language differs from the language the person is writing in. This goes beyond the schema's generic description and helps the agent choose the correct value.

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 states a specific verb and resource: "Builds a complete quotation or invoice from line items," optionally starting from a template and totaling it. This clearly distinguishes it from sibling tools like calculate_totals, get_template, and search_templates by emphasizing the end-to-end document-building behavior and the returned URL.

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

Usage Guidelines4/5

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

The description gives clear context for when to use the tool: when building a complete quotation or invoice, and it adds operational guidance such as passing interfaceLanguage when the document language differs from the user's language. It does not explicitly name alternatives or say when not to use it, but the context is strong enough for an agent to route correctly.

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

All QuoteBill tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.