Skip to main content
Glama

Render invoice text

render_invoice_text
Read-onlyIdempotent

Build an invoice from the same inputs as create_invoice and return it as a plain-text document (header, line items, subtotal, discount, tax, TOTAL DUE, notes) ready to paste into an email or message. Use when the user wants readable invoice text. Do NOT use when structured fields are needed; use create_invoice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesLine items (at least one), each {description, quantity, unit_price}; line amount = quantity x unit_price.
notesNoFree-text notes printed on the invoice, e.g. payment instructions. Default empty.
currencyNoThree-letter currency code, case-insensitive: one of USD, EUR, INR, GBP, AED, SGD, AUD, CAD. Default USD.
client_nameYesName of the client being billed, e.g. "Globex Corp"
due_in_daysNoPayment term in days from today; sets due_date and 'Net N' terms. Default 14.
discount_pctNoDiscount in percent of the subtotal, 0-100, e.g. 10 for 10% off. Default 0.
tax_rate_pctNoTax rate in percent, 0-100, applied after the discount, e.g. 18 for 18% GST. Default 0.
business_nameYesName of the business or freelancer issuing the invoice, e.g. "Acme Design Studio"
invoice_numberNoInvoice number to use, e.g. "INV-2026-042". If omitted, one is generated as INV-YYYYMMDD-NNNN.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe invoice rendered as multi-line plain text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed18 schema fields changed
    • changedInput schema / properties / business_name / description
      Previous value: -"The business name for this request."New value: +"Name of the business or freelancer issuing the invoice, e.g. \"Acme Design Studio\""
    • addedInput schema / properties / business_name / minLength
      Added value: +1
    • changedInput schema / properties / client_name / description
      Previous value: -"The client name for this request."New value: +"Name of the client being billed, e.g. \"Globex Corp\""
    • addedInput schema / properties / client_name / minLength
      Added value: +1
    • changedInput schema / properties / currency / description
      Previous value: -"Three-letter ISO currency code (e.g. USD)."New value: +"Three-letter currency code, case-insensitive: one of USD, EUR, INR, GBP, AED, SGD, AUD, CAD. Default USD."
    • changedInput schema / properties / discount_pct / description
      Previous value: -"Discount pct as a number (e.g. 8.5 means 8.5%)."New value: +"Discount in percent of the subtotal, 0-100, e.g. 10 for 10% off. Default 0."
    • addedInput schema / properties / discount_pct / maximum
      Added value: +100
    • addedInput schema / properties / discount_pct / minimum
      Added value: +0
    • changedInput schema / properties / due_in_days / description
      Previous value: -"The due in days as a number."New value: +"Payment term in days from today; sets due_date and 'Net N' terms. Default 14."
    • changedInput schema / properties / invoice_number / description
      Previous value: -"The invoice number for this request."New value: +"Invoice number to use, e.g. \"INV-2026-042\". If omitted, one is generated as INV-YYYYMMDD-NNNN."
    • changedInput schema / properties / items / description
      Previous value: -"List of items values."New value: +"Line items (at least one), each {description, quantity, unit_price}; line amount = quantity x unit_price."
    • addedInput schema / properties / items / items
      Added value: +{
      +  "properties": {
      +    "description": {
      +      "description": "What was sold or done, e.g. \"Logo design\" or \"Consulting hours\"",
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    "quantity": {
      +      "description": "Quantity or hours, must be > 0, e.g. 10",
      +      "exclusiveMinimum": 0,
      +      "type": "number"
      +    },
      +    "unit_price": {
      +      "description": "Price per unit in the invoice currency, >= 0, e.g. 50",
      +      "minimum": 0,
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "description",
      +    "quantity",
      +    "unit_price"
      +  ],
      +  "type": "object"
      +}
    • addedInput schema / properties / items / minItems
      Added value: +1
    • changedInput schema / properties / notes / description
      Previous value: -"The notes for this request."New value: +"Free-text notes printed on the invoice, e.g. payment instructions. Default empty."
    • changedInput schema / properties / tax_rate_pct / description
      Previous value: -"Tax rate pct as a number (e.g. 8.5 means 8.5%)."New value: +"Tax rate in percent, 0-100, applied after the discount, e.g. 18 for 18% GST. Default 0."
    • addedInput schema / properties / tax_rate_pct / maximum
      Added value: +100
    • addedInput schema / properties / tax_rate_pct / minimum
      Added value: +0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "text": {
      +      "description": "The invoice rendered as multi-line plain text.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "text"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "invoice_text": {
      -      "description": "The rendered invoice as plain text.",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "invoice_text"
      -  ],
      -  "type": "object"
      -}New value: +null
  3. Changed10 schema fields changed
    • addedInput schema / properties / business_name / description
      Added value: +"The business name for this request."
    • addedInput schema / properties / client_name / description
      Added value: +"The client name for this request."
    • addedInput schema / properties / currency / description
      Added value: +"Three-letter ISO currency code (e.g. USD)."
    • addedInput schema / properties / discount_pct / description
      Added value: +"Discount pct as a number (e.g. 8.5 means 8.5%)."
    • addedInput schema / properties / due_in_days / description
      Added value: +"The due in days as a number."
    • addedInput schema / properties / invoice_number / description
      Added value: +"The invoice number for this request."
    • addedInput schema / properties / items / description
      Added value: +"List of items values."
    • addedInput schema / properties / notes / description
      Added value: +"The notes for this request."
    • addedInput schema / properties / tax_rate_pct / description
      Added value: +"Tax rate pct as a number (e.g. 8.5 means 8.5%)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "invoice_text": {
      +      "description": "The rendered invoice as plain text.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "invoice_text"
      +  ],
      +  "type": "object"
      +}
  4. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description still adds real value by enumerating the rendered sections (header, line items, subtotal, discount, tax, TOTAL DUE, notes) and the intended destination ('paste into an email or message'), which tells the agent this is a formatting step, not a persistence step.

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 sentences, zero padding. The output shape is front-loaded, then the use case, then the exclusion — the ordering an agent needs for a fast routing decision.

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?

An output schema exists, so return values need not be spelled out, and annotations carry the safety/idempotency semantics. What remains — when to pick this versus create_invoice, and what the rendered text contains — is fully covered.

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 description coverage is 100%, so the baseline is 3. The description adds a cross-tool contract fact beyond the schema: the inputs are the 'same inputs as create_invoice', telling the agent the parameter shape is shared with a sibling rather than unique to this renderer.

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?

States a specific verb (Build/render) and resource (invoice) plus the exact output form: a plain-text document with header, line items, subtotal, discount, tax, TOTAL DUE and notes. It also explicitly names the sibling create_invoice as the contrasting tool, so the agent can separate the two without opening schemas.

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 both sides of the routing decision: 'Use when the user wants readable invoice text' and 'Do NOT use when structured fields are needed; use create_invoice.' The alternative tool is named with the condition that selects it.

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.