Skip to main content
Glama
Sign In

PineBill

by app.pinebill
OverviewDiscussionsAdmin

Email an estimate

send_estimate_email
Destructive

Email an existing estimate (with its PDF) to the customer. Resolve the estimate ID first with list_estimates if needed. If recipientEmails is omitted, the customer's saved email is used. The email can't be recalled once sent, so confirm the estimate and recipients with the user first.

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": {
      "estimateId": "<estimateId>"
    },
    "name": "send_estimate_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageNoOptional custom message to include in the estimate email
estimateIdYesEstimate ID to email
customerNameNoCustomer name for confirmation display
customerEmailNoSaved customer email for confirmation display
estimateNumberNoEstimate number for confirmation display
recipientEmailsNoOverride recipient emails. Omit to use the estimate customer's saved email.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior4/5

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

Adds genuine context beyond the annotations (destructiveHint=true, openWorldHint=true): the attachment behavior, the fallback to the customer's saved email, and the irreversibility of the send. It does not cover what a successful send returns or how duplicate/repeat sends behave, so it is strong but not exhaustive for an outbound-email mutation.

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?

Three short sentences, each carrying unique information: what is sent, how to obtain the ID, and the confirmation/irreversibility warning. The destructive risk is placed near the end where it lands as a caution, with no filler.

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 an irreversible outbound-email action with no output schema, the description covers the essential gaps: prerequisite lookup, recipient defaulting, and the cannot-recall warning. It stops short of describing delivery outcomes or failure modes, which would be needed for a 5.

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 estimateId and recipientEmails are already documented in the schema. The description reinforces the recipientEmails omission behavior but adds no new syntax, limits (e.g. max 5 recipients), or meaning for the display-only fields, so baseline 3 applies.

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 ('Email an existing estimate') plus what is transmitted ('with its PDF') and to whom ('to the customer'). The word 'estimate' cleanly separates it from the sibling send_invoice_email without needing to open either schema.

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 an explicit prerequisite ('Resolve the estimate ID first with list_estimates if needed') naming the sibling to use, and a gating instruction ('confirm the estimate and recipients with the user first'). It also states the condition under which recipientEmails is unnecessary.

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