Freelancer invoices with totals, tax, due dates. Free.
Scored across 4 tools
Each tool has a clearly distinct purpose, and the descriptions explicitly cross-reference each other with 'Do NOT use...' guidance. The potential overlap between create_invoice and render_invoice_text (same inputs, different output format) is cleanly delineated by the structured-vs-text distinction.
Three tools follow a consistent verb_noun pattern (calculate_totals, create_invoice, render_invoice_text), making the convention highly predictable. The one outlier, supported_currencies, is a noun phrase rather than an action, a minor deviation that is still readable.
Four tools is well-scoped for a focused invoice-generation domain. Each tool earns its place: math-only totals, structured invoice, text render, and a currency reference check.
The surface covers the core lifecycle of producing an invoice (compute, structure, render) plus a currency guardrail, and statelessness means update/delete are not applicable. Minor gaps remain, such as no tax-rate lookup or currency conversion, though the latter is explicitly disclaimed.
Compute subtotal, discount, tax and total for a list of line items (discount applied before tax, amounts rounded to 2 dp). Use for quick totals math without building an invoice. Do NOT use to produce an invoice document; use create_invoice.
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | Line items (at least one), each {description, quantity, unit_price}; line amount = quantity x unit_price. | |
| discount_pct | No | Discount in percent of the subtotal, 0-100, e.g. 10 for 10% off. Default 0. | |
| tax_rate_pct | No | Tax rate in percent, 0-100, applied after the discount, e.g. 18 for 18% GST. Default 0. |
| Name | Required | Description |
|---|---|---|
| tax | Yes | Tax amount = (subtotal - discount) x tax_rate_pct / 100. |
| total | Yes | Final amount = subtotal - discount + tax. |
| discount | Yes | Discount amount = subtotal x discount_pct / 100. |
| subtotal | Yes | Sum of quantity x unit_price, rounded to 2 dp. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower; the description earns credit by disclosing the computation semantics the annotations cannot: discount is applied before tax and amounts are rounded to 2 dp. It does not cover edge behavior (e.g., empty or zero-value results, currency selection), so it falls short of 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, zero filler. The core computation and its ordering rule come first, and the routing exclusion follows immediately after.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
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 no explanation, and the schema fully documents the three parameters. With computation order, rounding, and the create_invoice boundary all stated, an agent has everything needed to call this correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 and the schema already documents units, ranges and defaults. The description adds meaning beyond the schema by fixing the ordering of discount_pct and tax_rate_pct ('discount applied before tax') and the rounding rule, which the field descriptions alone do not state.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a precise verb and the exact outputs ('subtotal, discount, tax and total') over a defined input ('list of line items'), and explicitly distinguishes itself from the sibling create_invoice. An agent can route between the two tools without opening either schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It states the positive case ('quick totals math without building an invoice') and an explicit exclusion with a named alternative ('Do NOT use to produce an invoice document; use create_invoice'). This is textbook when/when-not/alternative guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Build a complete invoice as structured data: invoice number, issue and due dates, line items, discount, tax, total and payment terms. Nothing is stored. Use when the user wants an invoice for a client. Do NOT use for totals only (use calculate_totals) or for a printable text version (use render_invoice_text).
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | Line items (at least one), each {description, quantity, unit_price}; line amount = quantity x unit_price. | |
| notes | No | Free-text notes printed on the invoice, e.g. payment instructions. Default empty. | |
| currency | No | Three-letter currency code, case-insensitive: one of USD, EUR, INR, GBP, AED, SGD, AUD, CAD. Default USD. | |
| client_name | Yes | Name of the client being billed, e.g. "Globex Corp" | |
| due_in_days | No | Payment term in days from today; sets due_date and 'Net N' terms. Default 14. | |
| discount_pct | No | Discount in percent of the subtotal, 0-100, e.g. 10 for 10% off. Default 0. | |
| tax_rate_pct | No | Tax rate in percent, 0-100, applied after the discount, e.g. 18 for 18% GST. Default 0. | |
| business_name | Yes | Name of the business or freelancer issuing the invoice, e.g. "Acme Design Studio" | |
| invoice_number | No | Invoice number to use, e.g. "INV-2026-042". If omitted, one is generated as INV-YYYYMMDD-NNNN. |
| Name | Required | Description |
|---|---|---|
| tax | Yes | Tax amount = (subtotal - discount) x tax_rate_pct / 100. |
| date | Yes | Issue date, today in UTC, YYYY-MM-DD. |
| items | Yes | Line items echoed back as provided. |
| notes | Yes | Notes text (empty string if none). |
| total | Yes | Amount due = subtotal - discount + tax. |
| symbol | Yes | Currency symbol used when rendering, e.g. $. |
| currency | Yes | Upper-case currency code, e.g. USD. |
| discount | Yes | Discount amount = subtotal x discount_pct / 100. |
| due_date | Yes | Due date, YYYY-MM-DD (issue date + due_in_days). |
| subtotal | Yes | Sum of quantity x unit_price, rounded to 2 dp. |
| client_name | Yes | Billed client name as given. |
| discount_pct | Yes | Discount percent that was applied. |
| tax_rate_pct | Yes | Tax rate percent that was applied. |
| business_name | Yes | Issuing business name as given. |
| payment_terms | Yes | Payment terms label, e.g. 'Net 14'. |
| invoice_number | Yes | Invoice number (given or generated INV-YYYYMMDD-NNNN). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so the safety profile is covered; the description adds the genuinely useful fact 'Nothing is stored,' clarifying this is pure computation with no persistence. It omits failure behavior (e.g., what happens on invalid line items), which is the only meaningful remaining gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three tight sentences: purpose and output shape first, then positive usage, then exclusions. Nothing is padded and the routing information is front-loaded where an agent will see it.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 9-parameter tool with an output schema and full annotation coverage, the description covers purpose, when-to-use, alternatives, and side-effect semantics. Required-parameter and value constraints are correctly left to the schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so every parameter (including nested item fields, currency list, and defaults) is already fully documented. The description's field list largely restates parameter names and adds only the derived outputs (issue date, total, 'Net N' terms), so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Build a complete invoice as structured data') and enumerates the artifacts produced: invoice number, dates, line items, discount, tax, total and payment terms. It also names the two siblings it is not, so an agent can discriminate without opening any schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicit routing: 'Use when the user wants an invoice for a client. Do NOT use for totals only (use calculate_totals) or for a printable text version (use render_invoice_text).' Both the positive trigger and the two exclusion conditions with named alternatives are present.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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.
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | Line items (at least one), each {description, quantity, unit_price}; line amount = quantity x unit_price. | |
| notes | No | Free-text notes printed on the invoice, e.g. payment instructions. Default empty. | |
| currency | No | Three-letter currency code, case-insensitive: one of USD, EUR, INR, GBP, AED, SGD, AUD, CAD. Default USD. | |
| client_name | Yes | Name of the client being billed, e.g. "Globex Corp" | |
| due_in_days | No | Payment term in days from today; sets due_date and 'Net N' terms. Default 14. | |
| discount_pct | No | Discount in percent of the subtotal, 0-100, e.g. 10 for 10% off. Default 0. | |
| tax_rate_pct | No | Tax rate in percent, 0-100, applied after the discount, e.g. 18 for 18% GST. Default 0. | |
| business_name | Yes | Name of the business or freelancer issuing the invoice, e.g. "Acme Design Studio" | |
| invoice_number | No | Invoice number to use, e.g. "INV-2026-042". If omitted, one is generated as INV-YYYYMMDD-NNNN. |
| Name | Required | Description |
|---|---|---|
| text | Yes | The invoice rendered as multi-line plain text. |
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.
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.
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.
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.
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.
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.
List the currency codes InvoiceGen accepts for invoices (USD, EUR, INR, GBP, AED, SGD, AUD, CAD). Use before create_invoice when unsure whether a currency is supported. No exchange rates or currency conversion are provided.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
| Name | Required | Description |
|---|---|---|
| currencies | Yes | Supported upper-case currency codes. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds a valuable scope boundary: no exchange rates or conversion are provided, preventing a false expectation about the tool's capability.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, front-loaded with the resource and its values, followed by usage guidance and then the scope limitation. No filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return format needn't be explained; the description instead supplies the value set, the invocation context, and the limitation. Nothing an agent needs to call this correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so per the rubric the baseline is 4. There is nothing for the description to clarify beyond confirming the parameterless nature of the call.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb-and-resource ('list the currency codes InvoiceGen accepts') and even enumerates the accepted values, so the agent knows exactly what comes back. It is trivially distinguishable from calculate_totals, create_invoice, and render_invoice_text.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says when to call it ('Use before create_invoice when unsure whether a currency is supported'), naming the sibling that motivates the call. The when-not condition is implied by 'when unsure', which is sufficient routing guidance for a static lookup.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
calculate_totals10 fields changedInput schema / properties / discount_pct / descriptionPrevious value: -"Discount rate as a percent, e.g. 10 for 10%"New value: +"Discount in percent of the subtotal, 0-100, e.g. 10 for 10% off. Default 0."Input schema / properties / discount_pct / maximumAdded value: +100Input schema / properties / discount_pct / minimumAdded value: +0Input schema / properties / items / descriptionPrevious value: -"List of items, each with name, quantity, and price"New value: +"Line items (at least one), each {description, quantity, unit_price}; line amount = quantity x unit_price."Input schema / properties / items / itemsAdded 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"
+}Input schema / properties / items / minItemsAdded value: +1Input schema / properties / tax_rate_pct / descriptionPrevious value: -"Tax rate as a percent, e.g. 8 for 8%"New value: +"Tax rate in percent, 0-100, applied after the discount, e.g. 18 for 18% GST. Default 0."Input schema / properties / tax_rate_pct / maximumAdded value: +100Input schema / properties / tax_rate_pct / minimumAdded value: +0Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "discount": {
+ "description": "Discount amount = subtotal x discount_pct / 100.",
+ "type": "number"
+ },
+ "subtotal": {
+ "description": "Sum of quantity x unit_price, rounded to 2 dp.",
+ "type": "number"
+ },
+ "tax": {
+ "description": "Tax amount = (subtotal - discount) x tax_rate_pct / 100.",
+ "type": "number"
+ },
+ "total": {
+ "description": "Final amount = subtotal - discount + tax.",
+ "type": "number"
+ }
+ },
+ "required": [
+ "subtotal",
+ "discount",
+ "tax",
+ "total"
+ ],
+ "type": "object"
+}create_invoice23 fields changedInput schema / properties / business_name / descriptionPrevious value: -"The name of the business issuing the invoice"New value: +"Name of the business or freelancer issuing the invoice, e.g. \"Acme Design Studio\""Input schema / properties / business_name / minLengthAdded value: +1Input schema / properties / client_name / descriptionPrevious value: -"The name of the client receiving the invoice"New value: +"Name of the client being billed, e.g. \"Globex Corp\""Input schema / properties / client_name / minLengthAdded value: +1Input schema / properties / currency / descriptionPrevious value: -"Currency code for the invoice, e.g. USD, EUR"New value: +"Three-letter currency code, case-insensitive: one of USD, EUR, INR, GBP, AED, SGD, AUD, CAD. Default USD."Input schema / properties / discount_pct / descriptionPrevious value: -"Discount rate as a percent, e.g. 10 for 10%"New value: +"Discount in percent of the subtotal, 0-100, e.g. 10 for 10% off. Default 0."Input schema / properties / discount_pct / maximumAdded value: +100Input schema / properties / discount_pct / minimumAdded value: +0Input schema / properties / due_in_days / descriptionPrevious value: -"Number of days until the invoice is due"New value: +"Payment term in days from today; sets due_date and 'Net N' terms. Default 14."Input schema / properties / invoice_number / descriptionPrevious value: -"Unique identifier for the invoice"New value: +"Invoice number to use, e.g. \"INV-2026-042\". If omitted, one is generated as INV-YYYYMMDD-NNNN."Input schema / properties / items / descriptionPrevious value: -"Array of objects, each with name, quantity, and unit_price"New value: +"Line items (at least one), each {description, quantity, unit_price}; line amount = quantity x unit_price."Input schema / properties / items / items / properties / description / descriptionAdded value: +"What was sold or done, e.g. \"Logo design\" or \"Consulting hours\""Input schema / properties / items / items / properties / description / minLengthAdded value: +1Input schema / properties / items / items / properties / quantity / descriptionAdded value: +"Quantity or hours, must be > 0, e.g. 10"Input schema / properties / items / items / properties / quantity / exclusiveMinimumAdded value: +0Input schema / properties / items / items / properties / unit_price / descriptionAdded value: +"Price per unit in the invoice currency, >= 0, e.g. 50"Input schema / properties / items / items / properties / unit_price / minimumAdded value: +0Input schema / properties / items / minItemsAdded value: +1Input schema / properties / notes / descriptionPrevious value: -"Any additional notes or comments for the invoice"New value: +"Free-text notes printed on the invoice, e.g. payment instructions. Default empty."Input schema / properties / tax_rate_pct / descriptionPrevious value: -"Tax rate as a percent, e.g. 20 for 20%"New value: +"Tax rate in percent, 0-100, applied after the discount, e.g. 18 for 18% GST. Default 0."Input schema / properties / tax_rate_pct / maximumAdded value: +100Input schema / properties / tax_rate_pct / minimumAdded value: +0Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "business_name": {
+ "description": "Issuing business name as given.",
+ "type": "string"
+ },
+ "client_name": {
+ "description": "Billed client name as given.",
+ "type": "string"
+ },
+ "currency": {
+ "description": "Upper-case currency code, e.g. USD.",
+ "type": "string"
+ },
+ "date": {
+ "description": "Issue date, today in UTC, YYYY-MM-DD.",
+ "type": "string"
+ },
+ "discount": {
+ "description": "Discount amount = subtotal x discount_pct / 100.",
+ "type": "number"
+ },
+ "discount_pct": {
+ "description": "Discount percent that was applied.",
+ "type": "number"
+ },
+ "due_date": {
+ "description": "Due date, YYYY-MM-DD (issue date + due_in_days).",
+ "type": "string"
+ },
+ "invoice_number": {
+ "description": "Invoice number (given or generated INV-YYYYMMDD-NNNN).",
+ "type": "string"
+ },
+ "items": {
+ "description": "Line items echoed back as provided.",
+ "items": {
+ "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"
+ },
+ "type": "array"
+ },
+ "notes": {
+ "description": "Notes text (empty string if none).",
+ "type": "string"
+ },
+ "payment_terms": {
+ "description": "Payment terms label, e.g. 'Net 14'.",
+ "type": "string"
+ },
+ "subtotal": {
+ "description": "Sum of quantity x unit_price, rounded to 2 dp.",
+ "type": "number"
+ },
+ "symbol": {
+ "description": "Currency symbol used when rendering, e.g. $.",
+ "type": "string"
+ },
+ "tax": {
+ "description": "Tax amount = (subtotal - discount) x tax_rate_pct / 100.",
+ "type": "number"
+ },
+ "tax_rate_pct": {
+ "description": "Tax rate percent that was applied.",
+ "type": "number"
+ },
+ "total": {
+ "description": "Amount due = subtotal - discount + tax.",
+ "type": "number"
+ }
+ },
+ "required": [
+ "invoice_number",
+ "date",
+ "due_date",
+ "business_name",
+ "client_name",
+ "currency",
+ "symbol",
+ "items",
+ "tax_rate_pct",
+ "discount_pct",
+ "subtotal",
+ "discount",
+ "tax",
+ "total",
+ "notes",
+ "payment_terms"
+ ],
+ "type": "object"
+}render_invoice_text18 fields changedInput schema / properties / business_name / descriptionPrevious value: -"The business name for this request."New value: +"Name of the business or freelancer issuing the invoice, e.g. \"Acme Design Studio\""Input schema / properties / business_name / minLengthAdded value: +1Input schema / properties / client_name / descriptionPrevious value: -"The client name for this request."New value: +"Name of the client being billed, e.g. \"Globex Corp\""Input schema / properties / client_name / minLengthAdded value: +1Input schema / properties / currency / descriptionPrevious 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."Input schema / properties / discount_pct / descriptionPrevious 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."Input schema / properties / discount_pct / maximumAdded value: +100Input schema / properties / discount_pct / minimumAdded value: +0Input schema / properties / due_in_days / descriptionPrevious 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."Input schema / properties / invoice_number / descriptionPrevious 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."Input schema / properties / items / descriptionPrevious value: -"List of items values."New value: +"Line items (at least one), each {description, quantity, unit_price}; line amount = quantity x unit_price."Input schema / properties / items / itemsAdded 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"
+}Input schema / properties / items / minItemsAdded value: +1Input schema / properties / notes / descriptionPrevious value: -"The notes for this request."New value: +"Free-text notes printed on the invoice, e.g. payment instructions. Default empty."Input schema / properties / tax_rate_pct / descriptionPrevious 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."Input schema / properties / tax_rate_pct / maximumAdded value: +100Input schema / properties / tax_rate_pct / minimumAdded value: +0Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "text": {
+ "description": "The invoice rendered as multi-line plain text.",
+ "type": "string"
+ }
+ },
+ "required": [
+ "text"
+ ],
+ "type": "object"
+}supported_currencies1 field changedOutput schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "currencies": {
+ "description": "Supported upper-case currency codes.",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "currencies"
+ ],
+ "type": "object"
+}calculate_totals1 field changedOutput schema / (root)Previous value: -{
- "properties": {
- "discount_amount": {
- "description": "The total discount applied to the subtotal.",
- "type": "number"
- },
- "subtotal": {
- "description": "The sum of all item prices before any discounts or taxes.",
- "type": "number"
- },
- "tax_amount": {
- "description": "The total tax applied to the subtotal after discount.",
- "type": "number"
- },
- "total": {
- "description": "The final amount after applying discount and tax to the subtotal.",
- "type": "number"
- }
- },
- "required": [
- "subtotal",
- "discount_amount",
- "tax_amount",
- "total"
- ],
- "type": "object"
-}New value: +nullcreate_invoice1 field changedOutput schema / (root)Previous value: -{
- "properties": {
- "business_name": {
- "description": "The name of the business issuing the invoice.",
- "type": "string"
- },
- "client_name": {
- "description": "The name of the client receiving the invoice.",
- "type": "string"
- },
- "currency": {
- "description": "The currency in which the invoice is denominated.",
- "type": "string"
- },
- "discount_amount": {
- "description": "The amount of discount applied to the subtotal.",
- "type": "number"
- },
- "due_date": {
- "description": "The date by which the invoice should be paid.",
- "format": "date",
- "type": "string"
- },
- "invoice_date": {
- "description": "The date when the invoice was created.",
- "format": "date",
- "type": "string"
- },
- "invoice_number": {
- "description": "The unique identifier for the invoice.",
- "type": "string"
- },
- "items": {
- "description": "The list of items included in the invoice.",
- "items": {
- "properties": {
- "description": {
- "description": "A brief description of the item.",
- "type": "string"
- },
- "quantity": {
- "description": "The quantity of the item.",
- "type": "number"
- },
- "total_price": {
- "description": "The total price for the quantity of the item.",
- "type": "number"
- },
- "unit_price": {
- "description": "The price per unit of the item.",
- "type": "number"
- }
- },
- "required": [
- "description",
- "quantity",
- "unit_price",
- "total_price"
- ],
- "type": "object"
- },
- "type": "array"
- },
- "notes": {
- "description": "Any additional notes or comments related to the invoice.",
- "type": "string"
- },
- "subtotal": {
- "description": "The total amount before tax and discount.",
- "type": "number"
- },
- "tax_amount": {
- "description": "The amount of tax applied to the subtotal.",
- "type": "number"
- },
- "total": {
- "description": "The final amount to be paid, after tax and discount.",
- "type": "number"
- }
- },
- "required": [
- "invoice_number",
- "business_name",
- "client_name",
- "invoice_date",
- "due_date",
- "currency",
- "subtotal",
- "tax_amount",
- "discount_amount",
- "total",
- "items"
- ],
- "type": "object"
-}New value: +nullrender_invoice_text1 field changedOutput schema / (root)Previous value: -{
- "properties": {
- "invoice_text": {
- "description": "The rendered invoice as plain text.",
- "type": "string"
- }
- },
- "required": [
- "invoice_text"
- ],
- "type": "object"
-}New value: +nullsupported_currencies1 field changedOutput schema / (root)Previous value: -{
- "properties": {
- "results": {
- "description": "List of supported currencies entries.",
- "items": {
- "properties": {
- "currencyCode": {
- "description": "The ISO 4217 currency code.",
- "type": "string"
- },
- "currencyName": {
- "description": "The full name of the currency.",
- "type": "string"
- },
- "currencySymbol": {
- "description": "The symbol used to represent the currency.",
- "type": "string"
- },
- "decimalPlaces": {
- "description": "The number of decimal places used by the currency.",
- "type": "integer"
- }
- },
- "required": [
- "currencyCode",
- "currencySymbol",
- "currencyName",
- "decimalPlaces"
- ],
- "type": "object"
- },
- "type": "array"
- }
- },
- "required": [
- "results"
- ],
- "type": "object"
-}New value: +nullcalculate_totals4 fields changedInput schema / properties / discount_pct / descriptionAdded value: +"Discount rate as a percent, e.g. 10 for 10%"Input schema / properties / items / descriptionAdded value: +"List of items, each with name, quantity, and price"Input schema / properties / tax_rate_pct / descriptionAdded value: +"Tax rate as a percent, e.g. 8 for 8%"Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "discount_amount": {
+ "description": "The total discount applied to the subtotal.",
+ "type": "number"
+ },
+ "subtotal": {
+ "description": "The sum of all item prices before any discounts or taxes.",
+ "type": "number"
+ },
+ "tax_amount": {
+ "description": "The total tax applied to the subtotal after discount.",
+ "type": "number"
+ },
+ "total": {
+ "description": "The final amount after applying discount and tax to the subtotal.",
+ "type": "number"
+ }
+ },
+ "required": [
+ "subtotal",
+ "discount_amount",
+ "tax_amount",
+ "total"
+ ],
+ "type": "object"
+}create_invoice10 fields changedInput schema / properties / business_name / descriptionAdded value: +"The name of the business issuing the invoice"Input schema / properties / client_name / descriptionAdded value: +"The name of the client receiving the invoice"Input schema / properties / currency / descriptionAdded value: +"Currency code for the invoice, e.g. USD, EUR"Input schema / properties / discount_pct / descriptionAdded value: +"Discount rate as a percent, e.g. 10 for 10%"Input schema / properties / due_in_days / descriptionAdded value: +"Number of days until the invoice is due"Input schema / properties / invoice_number / descriptionAdded value: +"Unique identifier for the invoice"Input schema / properties / items / descriptionAdded value: +"Array of objects, each with name, quantity, and unit_price"Input schema / properties / notes / descriptionAdded value: +"Any additional notes or comments for the invoice"Input schema / properties / tax_rate_pct / descriptionAdded value: +"Tax rate as a percent, e.g. 20 for 20%"Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "business_name": {
+ "description": "The name of the business issuing the invoice.",
+ "type": "string"
+ },
+ "client_name": {
+ "description": "The name of the client receiving the invoice.",
+ "type": "string"
+ },
+ "currency": {
+ "description": "The currency in which the invoice is denominated.",
+ "type": "string"
+ },
+ "discount_amount": {
+ "description": "The amount of discount applied to the subtotal.",
+ "type": "number"
+ },
+ "due_date": {
+ "description": "The date by which the invoice should be paid.",
+ "format": "date",
+ "type": "string"
+ },
+ "invoice_date": {
+ "description": "The date when the invoice was created.",
+ "format": "date",
+ "type": "string"
+ },
+ "invoice_number": {
+ "description": "The unique identifier for the invoice.",
+ "type": "string"
+ },
+ "items": {
+ "description": "The list of items included in the invoice.",
+ "items": {
+ "properties": {
+ "description": {
+ "description": "A brief description of the item.",
+ "type": "string"
+ },
+ "quantity": {
+ "description": "The quantity of the item.",
+ "type": "number"
+ },
+ "total_price": {
+ "description": "The total price for the quantity of the item.",
+ "type": "number"
+ },
+ "unit_price": {
+ "description": "The price per unit of the item.",
+ "type": "number"
+ }
+ },
+ "required": [
+ "description",
+ "quantity",
+ "unit_price",
+ "total_price"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "notes": {
+ "description": "Any additional notes or comments related to the invoice.",
+ "type": "string"
+ },
+ "subtotal": {
+ "description": "The total amount before tax and discount.",
+ "type": "number"
+ },
+ "tax_amount": {
+ "description": "The amount of tax applied to the subtotal.",
+ "type": "number"
+ },
+ "total": {
+ "description": "The final amount to be paid, after tax and discount.",
+ "type": "number"
+ }
+ },
+ "required": [
+ "invoice_number",
+ "business_name",
+ "client_name",
+ "invoice_date",
+ "due_date",
+ "currency",
+ "subtotal",
+ "tax_amount",
+ "discount_amount",
+ "total",
+ "items"
+ ],
+ "type": "object"
+}render_invoice_text10 fields changedInput schema / properties / business_name / descriptionAdded value: +"The business name for this request."Input schema / properties / client_name / descriptionAdded value: +"The client name for this request."Input schema / properties / currency / descriptionAdded value: +"Three-letter ISO currency code (e.g. USD)."Input schema / properties / discount_pct / descriptionAdded value: +"Discount pct as a number (e.g. 8.5 means 8.5%)."Input schema / properties / due_in_days / descriptionAdded value: +"The due in days as a number."Input schema / properties / invoice_number / descriptionAdded value: +"The invoice number for this request."Input schema / properties / items / descriptionAdded value: +"List of items values."Input schema / properties / notes / descriptionAdded value: +"The notes for this request."Input schema / properties / tax_rate_pct / descriptionAdded value: +"Tax rate pct as a number (e.g. 8.5 means 8.5%)."Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "invoice_text": {
+ "description": "The rendered invoice as plain text.",
+ "type": "string"
+ }
+ },
+ "required": [
+ "invoice_text"
+ ],
+ "type": "object"
+}supported_currencies1 field changedOutput schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "results": {
+ "description": "List of supported currencies entries.",
+ "items": {
+ "properties": {
+ "currencyCode": {
+ "description": "The ISO 4217 currency code.",
+ "type": "string"
+ },
+ "currencyName": {
+ "description": "The full name of the currency.",
+ "type": "string"
+ },
+ "currencySymbol": {
+ "description": "The symbol used to represent the currency.",
+ "type": "string"
+ },
+ "decimalPlaces": {
+ "description": "The number of decimal places used by the currency.",
+ "type": "integer"
+ }
+ },
+ "required": [
+ "currencyCode",
+ "currencySymbol",
+ "currencyName",
+ "decimalPlaces"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "results"
+ ],
+ "type": "object"
+}calculate_totalscreate_invoicerender_invoice_textsupported_currenciesCreate, send and track invoices for freelancers and small businesses.
Freelancer invoice generator: line items, tax, totals, PDF - issued from a chat message.
Compliant invoicing for freelancers: create, issue and track invoices from your AI agent.
Freelancer time tracking: log time, run timers, manage clients and projects, make invoices.
Add one secure layer between your agents and this server.
