BeeL MCP server

Official

Overview Schema Source Related Servers Discussions Admin

beel_create_series

Idempotent

Create an invoice series under a company to assign fiscal numbering by document type, format, and reset policy while enforcing unique codes and AEAT-compliant numbers.

Instructions

Creates an invoice series under a company.

Document type: document_type is required. UNASSIGNED is rejected with 422 SERIES_UNASSIGNED_TYPE_NOT_ALLOWED: corrective invoices need a series of their own.
Code: must be unique within the company; a code already taken answers 409.
Unique numbers per issuer: a series whose code and format could print a number that another series of the company (in the same environment, active or not) can also print is rejected with 409 SERIES_FORMAT_OVERLAPS, naming that series. Proforma series are not compared.
Numbering: format must contain {NUM} or {NUM:X} and only accepts uppercase tokens. counter_reset defaults to ANNUAL, so a format with no year token has to be sent with counter_reset: NEVER.
Default series: the first series created for a document type is marked as default even if you send default_series: false.

Endpoint: POST /v1/companies/{company_id}/series

⚠️ Read before calling:

Fiscal rules, domains numbering: beel_rules_list with domain, or resource beel://guardrails/.
How a series formats numbers, and which series configurations are rejected. (resource: beel://guardrails/series-and-numbering)

Input Schema

TableJSON Schema

Name	Required	Description
`body`	Yes
`company_id`	Yes	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.
`idempotency_key`	No	Optional 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.

Changed5 schema fields changedv0.9.0Oct 1, 2026

addedInput schema / $defs / CreateSeriesRequest / description

Added value: +"Request to create an invoice series. `document_type` is required: a new series always has\na type, and `UNASSIGNED` is rejected with `422 SERIES_UNASSIGNED_TYPE_NOT_ALLOWED`.\nCorrective invoices need a series of their own (`CORRECTIVE`).\n"

changedInput schema / $defs / CreateSeriesRequest / properties / initial_number / description

Previous value: -"Initial number for this series counter.\nUseful when migrating from another system and wanting to continue existing numbering.\nFor example, if the last invoices were 2024-0150, you can set initial_number=151.\nDefault value is 1.\n"New value: +"Initial number for this series counter.\nUseful when migrating from another system and wanting to continue existing numbering.\nFor example, if the last invoices were 2024-0150, you can set initial_number=151.\nDefault value is 1.\nIt applies only to the first period in which the series issues an invoice: with\n`counter_reset: ANNUAL` or `MONTHLY`, every later year or month starts at 1. With\n`NEVER` there is a single period, so numbering simply continues from it.\n"

changedInput schema / $defs / CreateSeriesRequest / required

Previous value: -[
-  "name",
-  "code",
-  "format"
-]New value: +[
+  "document_type",
+  "name",
+  "code",
+  "format"
+]

changedInput schema / $defs / DocumentType / description

Previous value: -"Document type associated with a series. Values mirror `InvoiceType`,\nso the series a document needs is named exactly like the document:\n- UNASSIGNED: Legacy series, compatible with any invoice type\n- STANDARD: Standard invoice\n- SIMPLIFIED: Simplified invoice\n- CORRECTIVE: Corrects or cancels a previous invoice\n- PROFORMA: Proforma (commercial document, non-fiscal numbering)\n"New value: +"Document type associated with a series. Values mirror `InvoiceType`,\nso the series a document needs is named exactly like the document:\n- UNASSIGNED: Legacy value of series created before types existed. A series numbers only\n  documents of its own type, so an `UNASSIGNED` series numbers none\n  (`422 SERIES_INCOMPATIBLE_DOC_TYPE`); give it a type to keep using it. No series can be\n  created with it or moved to it (`422 SERIES_UNASSIGNED_TYPE_NOT_ALLOWED`). The live\n  ones were given the type they numbered most.\n- STANDARD: Standard invoice\n- SIMPLIFIED: Simplified invoice\n- CORRECTIVE: Corrects or cancels a previous invoice\n- PROFORMA: Proforma (commercial document, non-fiscal numbering)\n"

changedInput schema / $defs / SeriesFormat / description

Previous value: -"Format template with available variables (UPPERCASE ONLY):\n- {CODIGO}: Series code (e.g., \"FAC\")\n- {YYYY}: Year with 4 digits (e.g., \"2025\")\n- {YY}: Year with 2 digits (e.g., \"25\")\n- {MM}: Month with 2 digits (e.g., \"01\")\n- {NUM}: Sequential number without padding (e.g., \"1\")\n- {NUM:X}: Sequential number with padding (e.g., {NUM:4} → \"0001\")\n\n**REQUIRED**: Must contain at least {NUM} or {NUM:X}\n**IMPORTANT**: Only uppercase (rejects {yy}, {mm}, {codigo}, etc.)\n\nValid examples:\n- \"{CODIGO}-{YYYY}-{NUM:4}\" → \"FAC-2025-0001\"\n- \"{CODIGO}/{NUM:6}\" → \"FAC/000001\"\n- \"{YYYY}{MM}-{NUM:3}\" → \"202501-001\"\n"New value: +"Format template with available variables (UPPERCASE ONLY):\n- {CODIGO}: Series code (e.g., \"FAC\")\n- {YYYY}: Year with 4 digits (e.g., \"2025\")\n- {YY}: Year with 2 digits (e.g., \"25\")\n- {MM}: Month with 2 digits (e.g., \"01\")\n- {NUM}: Sequential number without padding (e.g., \"1\")\n- {NUM:X}: Sequential number with padding (e.g., {NUM:4} → \"0001\")\n\n**REQUIRED**: Must contain at least {NUM} or {NUM:X}\n**IMPORTANT**: Only uppercase (rejects {yy}, {mm}, {codigo}, etc.)\n\nValid examples:\n- \"{CODIGO}-{YYYY}-{NUM:4}\" → \"FAC-2025-0001\"\n- \"{CODIGO}/{NUM:6}\" → \"FAC/000001\"\n- \"{YYYY}{MM}-{NUM:3}\" → \"202501-001\"\n\nThe generated number is the invoice number sent to the AEAT, which accepts at most 60\nprintable ASCII characters and none of `\"`, `'`, `<`, `>`, `=`. A format whose longest\npossible number breaks that rule is rejected with `422 SERIES_FORMAT_NUMBER_TOO_LONG` or\n`SERIES_FORMAT_INVALID_CHARACTERS`. The counter counts as at least 9 digits, with or without\npadding: `{NUM:X}` is a minimum width, not a maximum.\n"

Changed8 schema fields changedv0.5.0Aug 30, 2026

addedInput schema / $defs / CreateSeriesRequest / additionalProperties
```
Added value: +false
```
removedInput schema / $defs / CreateSeriesRequest / properties / description / example
```
Removed value: -"Series for standard invoices"
```
removedInput schema / $defs / CreateSeriesRequest / properties / initial_number / example
```
Removed value: -1
```
removedInput schema / $defs / CreateSeriesRequest / properties / name / example
```
Removed value: -"Main Series"
```
removedInput schema / $defs / SeriesCode / example
```
Removed value: -"FAC"
```
removedInput schema / $defs / SeriesFormat / example
```
Removed value: -"{CODIGO}-{YYYY}-{NUM:4}"
```
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."

First observedv0.3.1Aug 25, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Discloses behavior well beyond the annotations: specific 409/422 error codes (SERIES_FORMAT_OVERLAPS, SERIES_UNASSIGNED_TYPE_NOT_ALLOWED, SERIES_FORMAT_NUMBER_TOO_LONG), cross-series overlap detection with proforma exemption, and the non-obvious side effect that the first series of a type is auto-promoted to default even when default_series:false is sent. These are exactly the mutation side effects an agent needs.

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, then structured bullets that each carry a distinct constraint or error code; nothing is filler and each sentence earns its place. It is long, but the length is justified by the density of real rules rather than repetition.

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 mutation tool with no output schema, the description covers creation rules, failure modes, side effects, and resource pointers thoroughly. It does not describe the success response shape beyond the default_series flag, but the error and side-effect coverage is strong enough to call it complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, and the description reinforces the highest-risk params with behavioral meaning: document_type rejection rule, code uniqueness, format {NUM}/{NUM:X} requirement, counter_reset default interaction with year tokens, and the default_series auto-promotion rule. It adds context beyond the schema for the critical fields, though name/active/description/initial_number are left entirely 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 precise verb+resource+scope: 'Creates an invoice series under a company,' plus the exact endpoint POST /v1/companies/{company_id}/series. An agent can distinguish this from sibling write tools like beel_set_default_series or beel_ensure_default_series immediately.

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 clear pre-call context (read beel_rules_list with a domain, or the beel://guardrails resources) and enumerates concrete rejection conditions that shape whether the call should proceed. It stops short of routing to alternatives such as patch_series or list_series, so it is clear context without explicit when-not/alternative guidance.

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

Deploy Server

beel_create_series

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools