Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_send_invoice

DestructiveIdempotent

Emails an invoice with its PDF attached, using default customer recipients when none are specified. Set recipients, CC, subject, message, and language to deliver the invoice directly.

Instructions

Sends the invoice by email, attaching its PDF by default. When no recipient is given, the addresses configured on the customer are used.

BeeL API endpoint: POST /v1/companies/{company_id}/invoices/{invoice_id}/send (reference: https://docs.beel.es)

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": {
      "company_id": "<company_id>",
      "invoice_id": "<invoice_id>"
    },
    "name": "beel_send_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
company_idYesUnique identifier (UUID) of the company the operation acts on — its identifier, not its NIF. It is the only source of context: the account that owns it is derived from it, and the `BeeL-Active-Company` header plays no part. A company you do not reach answers `403`, and so does a company that does not exist, so the existence of a company in another account is never disclosed.
invoice_idYesInvoice ID
idempotency_keyNoOptional idempotency key for this operation. Omit it and one is derived from the request itself, which makes a blind retry safe but also collapses a SECOND, deliberately identical operation into the first for 24 hours. Set it — to an order id, or anything unique per intended operation — whenever you mean to create something that may look identical to what you just created.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.10.0
    • addedInput schema / properties / body / type
      Added value: +"object"
    • addedInput schema / properties / invoice_id / type
      Added value: +"string"
  2. Changed3 schema fields changedv0.9.0
    • changedInput schema / $defs / Language / description
      Previous value: -"Supported languages"New value: +"Supported languages: `es` Spanish, `en` English, `ca` Catalan.\n"
    • changedInput schema / $defs / SendEmailRequest / properties / language / description
      Previous value: -"Email language. If not provided, uses the user's language (same fallback as the bulk send). Sin `default:` a propósito: quien resuelve el idioma es el servicio, no el DTO."New value: +"Language of the email. When omitted, the issuing company's `email_language` applies, and Spanish (`es`) when the company has none set."
    • changedInput schema / $defs / SendEmailRequest / properties / recipients / description
      Previous value: -"If not specified, uses the customer's email"New value: +"Recipients of the email. When omitted, the invoice's `email_config` recipients apply,\nthen the customer's `billing_emails`, then the customer's `email`.\n"
  3. Changed6 schema fields changedv0.5.0
    • removedInput schema / $defs / Email / example
      Removed value: -"user@example.com"
    • removedInput schema / $defs / Language / example
      Removed value: -"es"
    • addedInput schema / $defs / SendEmailRequest / additionalProperties
      Added value: +false
    • removedInput schema / $defs / UUID / example
      Removed value: -"550e8400-e29b-41d4-a716-446655440000"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / company_id / description
      Previous value: -"NIF (company) the operation acts on. It is the only source of context: the account that owns it is derived from it, and the `BeeL-Active-Company` header plays no part. A NIF you do not reach answers `403`, and so does a NIF that does not exist, so the existence of a NIF in another account is never disclosed."New value: +"Unique identifier (UUID) of the company the operation acts on — its identifier, not its NIF. It is the only source of context: the account that owns it is derived from it, and the `BeeL-Active-Company` header plays no part. A company you do not reach answers `403`, and so does a company that does not exist, so the existence of a company in another account is never disclosed."
  4. First observedv0.3.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructive=false? no — destructiveHint=true, openWorldHint=true and idempotentHint=true, and the description is consistent with that by framing it as an outward-facing send. It adds useful behavior beyond the annotations: PDF attachment is on by default and unspecified recipients resolve to configured customer addresses. It does not mention irreversibility of a sent email, delivery failure handling, or what is returned, which keeps it below a 5.

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?

Front-loaded with the core action and its default in one sentence, followed by the recipient fallback rule and a compact endpoint reference. No filler; the endpoint line is marginally useful context rather than agent-facing guidance.

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?

No output schema exists, yet the description covers the essential send semantics and the default attachment/recipient behavior, and annotations carry the risk profile. Gaps remain around the response (e.g., delivery record) and failure conditions, but the tool is simple enough (4 params, 2 required) that the definition is largely sufficient.

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 75%, so the schema already documents most parameters in depth (including the recipient fallback chain and attach_source_invoices error modes). The description only restates the recipient fallback and attach_pdf default, adding little that the schema does not already say.

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 states a specific verb and resource — sending an invoice by email — with the default behavior (PDF attached) and the fallback recipient source. It does not explicitly distinguish itself from near-neighbors such as beel_create_invoice_delivery or beel_preview/get_invoice_pdf, so an agent must infer the boundary.

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 implied by the action (deliver an existing invoice to recipients), and it notes the default-recipient case, but there is no explicit when-to-use/when-not guidance and no sibling alternative named for the email-delivery family.

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

Deploy Server

Other Tools