EosLog Free Tools

Create a quote PDF

create_quote_pdf

Makes a professional quote (estimate) 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, deposit, note and how many days the quote stays valid. EosLog adds up the subtotal, discount, tax and total, saves the quote 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 a quote or estimate 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_quote_pdf"
  }
}

Input Schema

Name	Required	Description
`title`	No	Optional subject line, for example Biweekly house cleaning.
`message`	No	Optional note to the customer.
`tax_rate`	No	Sales tax percent on the subtotal after any discount, for example 8.25. The user supplies it.
`line_items`	Yes	One row per service or item, with the prices the user gives.
`valid_days`	No	How many days the quote stays valid.
`business_name`	Yes	The business sending the document, as it should print at the top.
`customer_name`	No	Who the document is for, a person or a company. Printed as Customer when left out.
`business_email`	No	Business email to print on it.
`business_phone`	No	Business phone to print on it.
`deposit_percent`	No	Optional deposit to schedule the job, as a percent of the total.
`discount_percent`	No	Optional discount, as a percent off the subtotal.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 21, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations (write, non-idempotent, open-world), the description discloses that EosLog computes subtotal/discount/tax/total, stores the quote behind an unguessable link for 90 days, and returns both a view/download/email link and a direct PDF link. It also states the prices are the user's and are never set by the tool, which is important behavioral guidance.

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?

Three sentences with the core purpose front-loaded and no filler. The middle sentence is long because it enumerates inputs and outputs, but each clause carries information an agent needs.

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?

With no output schema, the description carries the return-value burden and does so: the shareable link, the PDF link, and the 90-day retention are all stated. Combined with the 100%-covered schema, 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.

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 real meaning by naming which inputs are optional (tax, discount, deposit, note, validity days) and by clarifying that line-item prices must come from the user rather than being inferred. It stops short of explaining format or unit conventions, which the schema already covers.

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 resource ('Makes a professional quote (estimate) PDF') and scopes it to a small service business, which separates it from the sibling create_invoice_pdf. An agent can tell what artifact it produces without opening the schema.

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?

'Use it when the user wants a quote or estimate to send a customer' gives a clear triggering condition. It never explicitly routes invoices to create_invoice_pdf, so the alternative is only implied rather than named.

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

All EosLog Free Tools 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.

Resources

Need Help?