Skip to main content
Glama
Sign In

PineBill

by app.pinebill
OverviewDiscussionsAdmin

Get estimate PDF link

get_estimate_pdf_url
Read-onlyIdempotent

Get a fresh download link for an estimate's PDF. Use it when the user wants to open, view, or download an estimate, or when an earlier link has expired. Find the estimate ID with list_estimates first. pdfUrl is a private, signed download link that expires at pdfUrlExpiresAt (1 hour). Give it to the user to open or download the PDF; don't put it in emails, notes, or anything that has to keep working.

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": {
      "id": "<id>"
    },
    "name": "get_estimate_pdf_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesEstimate ID (from list_estimates)

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: the link is private and signed, expires at pdfUrlExpiresAt after 1 hour, must be handed to the user, and must not be placed in emails, notes, or anything durable. That is exactly the operational behavior an agent needs and cannot infer from annotations.

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 purpose is front-loaded, then usage, prerequisite, return semantics, and handling caveat follow in a logical order. Every sentence carries a distinct, actionable fact with no restatement of the title or name.

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?

For a one-parameter read tool with no output schema, the description still names the return fields (pdfUrl, pdfUrlExpiresAt), their lifetime, their security properties, and how to handle them. Nothing an agent needs to invoke or use the result correctly is missing.

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% and the single 'id' parameter is already documented as coming from list_estimates, so the description adds little new field-level meaning. It does reinforce the provenance requirement in prose, which is a modest value add over 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 first sentence gives a specific verb and resource ('Get a fresh download link for an estimate's PDF') and the word 'fresh' plus the expiry discussion distinguishes it from a plain fetch. It is clearly separable from siblings like fetch_estimate (record data) and get_invoice_pdf_url (different resource).

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?

Explicit triggers are given ('when the user wants to open, view, or download an estimate, or when an earlier link has expired'), along with an explicit prerequisite ('Find the estimate ID with list_estimates first'). The only thing not stated is a when-not condition, but the prerequisite and expiry note effectively prevent misuse for stale links.

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

All PineBill toolsInspect
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