Skip to main content
Glama

Beleg per E-Mail senden

send_document
Destructive

Ausgestellten Beleg als PDF per E-Mail senden; bei Schweizer Konten liegt der QR-Zahlteil als zweiter Anhang bei (payment_slip). Ohne eigenes SMTP über brandbill (Reply-To: Rechnungs-E-Mail); sonst Absenderkonto bzw. Standardkonto.

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>",
      "to": "<to>",
      "subject": "<subject>",
      "body": "<body>"
    },
    "name": "send_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNo
idYesBeleg-ID
toYes
bodyYes
subjectYes
payment_slipNoSchweiz: QR-Zahlteil mitgeben (true) oder weglassen (false). Ohne Angabe gilt die Vorgabe des Belegs (hide_payment_qr)
mail_account_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / payment_slip
      Added value: +{
      +  "description": "Schweiz: QR-Zahlteil mitgeben (true) oder weglassen (false). Ohne Angabe gilt die Vorgabe des Belegs (hide_payment_qr)",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructive, non-idempotent, open-world behavior, so the description only needs to add beyond that. It does: it discloses the attachment layout (PDF plus QR payment slip for Swiss accounts), the Reply-To address behavior via brandbill, and the sender-account fallback. It stops short of saying whether the send is irreversible or what happens on delivery failure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence with the core action front-loaded and parenthetical technical details kept short. No filler, though the nested clauses about SMTP and account selection pack several ideas tightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, open-world, non-idempotent tool with no output schema, the description covers delivery mechanics well but omits failure behavior, retry/duplicate-send risk (relevant given idempotentHint=false), and the meaning of most parameters. Adequate but with clear gaps.

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 only 29% of 7 parameters, so the description should compensate more than it does. It clarifies the semantics of payment_slip (Swiss QR slip included or omitted) and indirectly explains mail_account_id through the 'Absenderkonto bzw. Standardkonto' fallback, but says nothing about to, cc, subject, body, or id.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Ausgestellten Beleg als PDF per E-Mail senden') and even specifies the attachment composition, so the action is unambiguous. It does not explicitly contrast itself with the close sibling send_contract, which keeps it from a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the word 'Ausgestellten' signals the document must already be issued/finalized, and the sender-account sentence implies a choice between provider mail and an own account. There is no explicit when-to-use or when-to-prefer-an-alternative statement.

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