Skip to main content
Glama

send_invoice

Email a Draft/Sent/Overdue invoice to its client (requires the client to have an email; counts against the monthly send quota). CONFIRM with the user before calling — this emails a real person.

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": "send_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does real work: it discloses an irreversible external side effect (emails a real person), a quota cost (counts against the monthly send quota), and a prerequisite on client data. It does not say whether the invoice status changes after sending or what a failure looks like.

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?

Two sentences, side effects and preconditions front-loaded, and the confirmation warning placed last as the final gate before a real email goes out. 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 a one-parameter mutation with no annotations and no output schema, the definition covers the prerequisites, cost, and confirmation requirement an agent needs. Remaining gaps are post-condition behavior (status transition) and error handling, which are secondary for a send action.

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 0% for the single required parameter, so the description must compensate. Saying "a Draft/Sent/Overdue invoice" does imply that `id` identifies an invoice and constrains its eligible statuses, but the UUID format and whether an ineligible status is rejected are left to 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?

States a concrete verb and resource ("Email a Draft/Sent/Overdue invoice to its client") plus the eligible invoice states. An agent can immediately separate this from send_document (documents) and create_invoice (creation), so no schema inspection is needed to know what it does.

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?

Gives a hard precondition (the client must have an email on file) and an operational gate (confirm with the user before calling). It stops short of naming alternatives or describing what to do when the precondition fails, so usage is clear but not fully routed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources