Skip to main content
Glama

Factuur versturen

send_invoice

Emails a final invoice as a PDF to the customer and copies the owner, requiring owner approval before sending.

Instructions

E-mail a final invoice as PDF to the customer, with a copy to the owner. Needs SMTP on the server. Ask the owner before sending; this leaves the building.

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": {
      "number": "<number>"
    },
    "name": "send_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOverrides the customer e-mail address
numberYesInvoice number, e.g. 2026-001
messageNoPlain-text body; a polite Dutch default is used when omitted

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true and destructiveHint=false, but the description adds genuinely non-obvious behavior: the message leaves the building irreversibly, a copy goes to the owner, the body is a PDF attachment, and SMTP must be configured. It still doesn't say what happens on delivery failure or what the response contains, so it is not fully transparent.

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, front-loading the action and recipients before the operational constraints. There is no redundant restatement of the title or schema.

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 a three-parameter, single-action tool with full schema coverage and no output schema, the description covers action, recipients, environment prerequisite, and approval workflow. Only the failure/return behavior is left unstated, which is a minor gap.

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 coverage is 100%, so 'to', 'number', and 'message' are already documented, including the Dutch default body. The description adds only implicit context — that the customer is the primary recipient and the owner receives a copy — without explaining the 'to' override or the invoice-number format. Baseline 3 is appropriate.

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 ('E-mail a final invoice as PDF to the customer, with a copy to the owner'), which cleanly separates it from sibling tools like create_invoice, finalize_invoice, and credit_invoice. The delivery channel (e-mail/PDF) and recipient set are named explicitly, so an agent can route correctly 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?

The description supplies a clear precondition ('Ask the owner before sending') and an environmental requirement ('Needs SMTP on the server'), which is real guidance about when this call is appropriate. It does not name an alternative tool or state when-not to use it, keeping it below a 5, but the 'final invoice' framing implies the invoice must already be final.

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