Skip to main content
Glama
Sign In

PineBill

by app.pinebill
OverviewDiscussionsAdmin

Get invoice PDF link

get_invoice_pdf_url
Read-onlyIdempotent

Get a fresh download link for an invoice's PDF. Use it when the user wants to open, view, or download an invoice, or when an earlier link has expired. Find the invoice ID with list_invoices 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_invoice_pdf_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesInvoice ID (from list_invoices)

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 say readOnly and idempotent, but they cannot convey that the returned link is private, signed, and expires in one hour. The description adds exactly the non-obvious traits that matter: freshness is guaranteed, the link is short-lived, and it must not be persisted in emails or notes.

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?

Four tight sentences ordered by purpose, trigger, prerequisite, and output semantics. No filler; the expiry and non-persistence warnings are front-loaded where the agent will act on them.

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?

Single-parameter read tool with no output schema, yet the description fully specifies the meaning and lifetime of the returned link (pdfUrl, pdfUrlExpiresAt, 1 hour) plus its handling constraints. Nothing needed to call 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 already says the ID comes from list_invoices, so the description mostly restates it. It does add mild reinforcement of provenance ('Find the invoice ID with list_invoices first'), just above the baseline.

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 ('Get a fresh download link for an invoice's PDF') and distinguishes itself from the sibling that produces the invoice content itself. An agent knows immediately this is a link-minting tool, not an invoice fetcher.

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?

Gives explicit triggers ('when the user wants to open, view, or download an invoice, or when an earlier link has expired') and a prerequisite workflow routing to list_invoices for the ID. It also states a negative constraint about where the link must not be placed, which is genuine when-not guidance.

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