Skip to main content
Glama

EosLog Free Tools

Create an invoice PDF

create_invoice_pdf

Makes a professional invoice PDF for a small service business from the details the user gives: the business name, the customer, and each line item's name, quantity and price, plus an optional tax rate, discount, payment terms, service date, invoice number and note. EosLog adds up the subtotal, discount, tax and total due, sets the due date from the payment terms, saves the invoice behind an unguessable link for 90 days, and returns that link (view, download or email the PDF) and a direct PDF link. Use it when the user wants an invoice to send a customer. It uses the user's prices and never sets them.

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": {
      "business_name": "<business_name>",
      "line_items": "<line_items>"
    },
    "name": "create_invoice_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoOptional note, such as how to pay.
tax_rateNoSales tax percent on the subtotal after any discount, for example 8.25. The user supplies it.
line_itemsYesOne row per service or item, with the prices the user gives.
service_dateNoOptional date or period of the work, as text, for example October 2026 or 10/1 to 10/15.
business_nameYesThe business sending the document, as it should print at the top.
customer_nameNoWho the document is for, a person or a company. Printed as Customer when left out.
payment_termsNoWhen payment is due: on receipt, or 15, 30 or 45 days after the invoice date.upon_receipt
business_emailNoBusiness email to print on it.
business_phoneNoBusiness phone to print on it.
invoice_numberNoOptional invoice number. One based on the date and time is used when left out.
discount_percentNoOptional discount, as a percent off the subtotal.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

goes well beyond the annotations (which only declare it is a non-idempotent write with open-world behavior) by disclosing that it computes subtotal/discount/tax/total, derives the due date from payment terms, retains the file behind an unguessable link for 90 days, and returns both a view/download/email link and a direct PDF link.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the outcome and zero filler, but the first sentence is a dense run-on enumerating every optional field, which slightly slows scanning. Still appropriately sized for an 11-parameter tool.

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?

Despite having no output schema, the description fully explains the return value (share link plus direct PDF link, 90-day retention) and the computed behavior, so an agent has everything needed to call it and report results.

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, but the description adds meaning by flagging which fields are optional (tax, discount, terms, date, number, note), clarifying that tax applies after discount, and emphasizing that prices are user-supplied and never set by the tool.

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 and artifact (creates an invoice PDF) with its scope (small service business, user-supplied prices) and distinguishes itself from the quote sibling by naming the exact document type produced.

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?

Explicitly says 'Use it when the user wants an invoice to send a customer', which gives a clear trigger. However it does not state when to prefer this over the sibling create_quote_pdf or any prerequisites/exclusions.

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