Skip to main content
Glama
beel-es

BeeL MCP server

Official
by beel-es
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

beel_send_invoice

Idempotent

Sends an invoice by email with PDF attachment by default. If no recipient is provided, it uses the customer's configured addresses.

Instructions

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

Endpoint: POST /v1/companies/{company_id}/invoices/{invoice_id}/send

Input Schema

TableJSON 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. 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"
  2. 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."
  3. First observedv0.3.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety and side-effect profile is largely covered. The description adds that the PDF is attached by default and that recipients fall back to customer configuration, but omits the external-email side effect, quota/sending restrictions, and any failure modes.

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?

Two tight sentences plus an endpoint line; the primary action is front-loaded and nothing is padded. The endpoint line is mildly redundant with the tool name but does add a concrete route.

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?

With no output schema, the description should say something about what a successful send yields (delivery record, id, status) and whether sending is reversible, and it does not. The schema covers the body parameters well, but the description leaves the post-send contract entirely unspecified.

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% and the nested body fields (recipients, cc, subject, language, attach_pdf, attach_source_invoices, idempotency_key) are richly documented in the schema. The description's recipient fallback statement is actually less precise than the schema's own precedence chain (email_config -> billing_emails -> email), so it adds no meaning beyond the schema. Baseline 3 applies.

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 ('Sends the invoice by email') and adds the endpoint path, so the action is unambiguous. It does not, however, differentiate from closely related siblings such as beel_create_invoice_delivery or beel_get_invoice_pdf, which an agent might reasonably confuse with this operation.

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?

'When no recipient is given, the addresses configured on the customer are used' documents a default path, which is genuine usage context. But there is no explicit when-to-use guidance versus alternatives (e.g. delivery records vs. sending) and no prerequisites or when-not conditions.

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