BeeL MCP server

Official

Overview Schema Source Related Servers Discussions Admin

beel_set_default_series

DestructiveIdempotent

Marks an invoice series as the default for a company and document type, and unmarks the previous default. The series must be active; repeating the call changes nothing.

Instructions

Marks an invoice series as the default of its document type for this company, and unmarks the previous one.

One per type: only one series can be the default per company and document type.
Must be active: an inactive series is rejected with 400.
Idempotent: repeating the call changes nothing.

BeeL API endpoint: PUT /v1/companies/{company_id}/series/{series_id}/default (reference: https://docs.beel.es)

⚠️ 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)

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>",
      "series_id": "<series_id>"
    },
    "name": "beel_set_default_series"
  }
}

Input Schema

Name	Required	Description	Default
`series_id`	Yes	Series ID to mark as default
`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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.10.0Nov 5, 2026
- addedInput schema / properties / series_id / type
```
Added value: +"string"
```

Changed3 schema fields changedv0.5.0Aug 30, 2026

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."

First observedv0.3.1Aug 25, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the annotations, the description explains exactly what gets changed (the previous default is unmarked), the one-per-type invariant, the 400 rejection for inactive series, and that repeat calls are no-ops. This is precisely the behavioral context needed for a destructive, idempotent mutation, and it is consistent with the supplied annotations.

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

Conciseness5/5

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

The main action and side effect are front-loaded, followed by scannable bullets for invariants and error behavior, then the endpoint and pre-call reading guidance. There is no wasted wording; even the repeated idempotency note reinforces the annotation.

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

Completeness5/5

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

For a two-parameter mutation with no output schema, the description covers side effects, preconditions, error behavior, idempotency, API endpoint, and relevant documentation resources. Nothing an agent needs in order to invoke it correctly is missing.

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 100%, with company_id and series_id already well documented in the schema. The description adds no parameter-level meaning beyond what the schema provides, so the baseline score 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 ('Marks an invoice series as the default of its document type') and adds the key side effect that the previous default is unmarked. It does not differentiate itself from the sibling beel_ensure_default_series, which is the most likely source of selection confusion.

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?

It gives useful preconditions ('Must be active') and points to guardrail resources to read before calling. However, it never says when to use this versus beel_ensure_default_series, beel_get_default_series, or beel_patch_series, leaving the agent to infer the distinction.

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

Deploy Server