Skip to main content
Glama

InvoiceQuick Free Invoice Generator

Generate free invoice

generate_free_invoice

Creates a free invoice as a PDF without an InvoiceQuick account and returns a preview link and a PDF link that work for 60 days. It does not email anyone. Ask the user for the sender and recipient details; do not invent names or email addresses.

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": {
      "title": "<title>",
      "bill_from": "<bill_from>",
      "bill_to": "<bill_to>",
      "items": "<items>"
    },
    "name": "generate_free_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesLine items.
notesNoNotes for the recipient. Links are not allowed.
titleYesShort description of the work, printed as the invoice subject.
due_atNoDue date, YYYY-MM-DD. Defaults to 30 days after the issue date.
bill_toYesWho the invoice is for.
bill_fromYesWho the invoice is from.
issued_atNoIssue date, YYYY-MM-DD. Defaults to today.
date_formatNoHow dates are printed on the PDF. Defaults to MM/DD/YYYY.
currency_codeNoISO code from list_currencies. Defaults to USD.
payment_termsNoPayment terms printed on the invoice. Links are not allowed.
invoice_numberNoDefaults to 1.
discount_percentNoDiscount on the whole invoice, in percent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that no account is required, that links work for 60 days, and that no email is sent to anyone. Those are meaningful behavioral details for an agent deciding whether and how to call it, though persistence and failure behavior are not covered.

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 front-loaded with the core action and output, followed by the no-email caveat and a concise data-sourcing instruction. Every sentence carries useful information with no redundancy.

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?

For a 12-parameter nested-object tool with no output schema, the description covers the key outcome (preview and PDF links valid for 60 days) and the no-email behavior. The schema handles parameter details, though the description could say more about persistence or error conditions.

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 the input schema already documents the parameters in detail. The description adds the useful sourcing rule to ask the user for sender and recipient details instead of inventing them, but it does not otherwise clarify parameter formats or defaults beyond the schema.

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: it creates a free invoice as a PDF, with no InvoiceQuick account required, and returns preview and PDF links. It also distinguishes the outcome from emailing, making the tool's function immediately clear.

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?

It establishes the key usage context that no account is needed and instructs the caller to ask the user for sender and recipient details rather than inventing them. It does not name alternatives or exclusions, but the guidance is clear for this tool.

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.

Resources