Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_create_invoice_delivery

DestructiveIdempotent

Sends multiple invoice PDFs as attachments in a single email to specified recipients and reports any invoices that could not be attached.

Instructions

Sends one email carrying the PDFs of several invoices of this company as attachments.

  • recipients: required, and must carry at least one address; no address is inferred from any profile.

  • Limit: up to 200 invoices per message (invoice_ids).

  • Failures: invoices whose PDF cannot be attached are reported in failures, and the message is still sent with the rest.

BeeL API endpoint: POST /v1/companies/{company_id}/invoices/deliveries (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>",
      "body": "<body>"
    },
    "name": "beel_create_invoice_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
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.
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. Changed1 schema field changedv0.10.0
    • addedInput schema / properties / body / type
      Added value: +"object"
  2. Changed1 schema field changedv0.9.0
    • changedInput schema / $defs / Language / description
      Previous value: -"Supported languages"New value: +"Supported languages: `es` Spanish, `en` English, `ca` Catalan.\n"
  3. Changed6 schema fields changedv0.5.0
    • addedInput schema / $defs / CreateInvoiceDeliveryRequest / additionalProperties
      Added value: +false
    • removedInput schema / $defs / Email / example
      Removed value: -"user@example.com"
    • removedInput schema / $defs / Language / example
      Removed value: -"es"
    • 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.6/5.0
Behavior4/5

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

Beyond the annotations (destructiveHint, idempotentHint, openWorldHint), the description discloses partial-failure semantics — invoices whose PDF cannot be attached land in `failures` and the message is still sent with the rest — which is real behavioral context an agent cannot get from the annotations. It also states no address is inferred from any profile, though it does not mention the destructive side effects of firing an irreversible external email.

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

Conciseness3/5

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

The front-loaded first sentence is good and the bullets are scannable, but two of the three bullets duplicate schema constraints (minItems, maxItems: 200), and the trailing endpoint/URL line is metadata rather than guidance for the agent.

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?

With no output schema, the description does the important work of naming the `failures` field and the still-sent behavior, which is exactly what an agent needs to interpret the result. Nesting and the cc/quota rules are left to the schema, which is reasonable given the tool's moderate complexity.

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 67%, so a baseline of 3 applies. What the description says about `recipients` and the 200-invoice limit largely restates the schema's minItems/maxItems and its recipients note, and it says nothing about `cc`, `subject`, `message`, `language`, or `idempotency_key` semantics.

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 opening sentence gives a specific verb and resource — sends one email carrying PDFs of several invoices as attachments — and the bullets scope it to a single message. It never names the sibling it is not, so an agent must infer the difference from beel_send_invoice or beel_get_invoice_pdf on its own.

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 by the constraints (at least one recipient, up to 200 invoice ids). There is no statement of when to choose this over beel_send_invoice for a single invoice, nor any prerequisite about the invoices needing to exist or be issued before delivery.

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