Skip to main content
Glama
beel-es

BeeL MCP server

Official
by beel-es

beel_ensure_default_series

Idempotent

Ensures a company always has default invoice series for standard, simplified, and corrective types, creating missing ones and returning the set. Idempotent: repeating does nothing.

Instructions

Ensures the company (NIF) has a default invoice series for STANDARD, SIMPLIFIED and CORRECTIVE in the current environment, and returns the resulting set. The request takes no body: the desired end state is one default per document type, so repeating it changes nothing.

A document type that already has a default keeps it, and it is returned unchanged. A missing one is created with code F, S or R and format {CODIGO}-{YYYY}-{NUM:4}, active and marked as default — unless that code is already taken by another series, in which case the type is omitted from the response and is left with no default.

Endpoint: PUT /v1/companies/{company_id}/series/defaults

⚠️ Fiscal guardrails — read before calling:

  • How invoice numbers are formed, and why numbering can never be rewritten. (resource: beel://guardrails/series-and-numbering)

For the exhaustive rules and worked examples, call beel_docs_search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesNIF (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.
Behavior5/5

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

Adds substantial behavior beyond annotations: creation codes (F, S, R), format {CODIGO}-{YYYY}-{NUM:4}, omitting types if code taken, and the fiscal guardrail warning. These details are not in annotations, which only declare idempotent and non-destructive.

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?

Structured with a clear opening sentence, then idempotency, behavior, endpoint, and guardrails. Each section adds necessary details; slightly long but justified for the fiscal complexity. The fiscal guardrail and docs pointer are front-loaded after the core purpose.

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?

Comprehensive for its complexity: explains the expected end state, edge cases (code conflicts), the endpoint, and fiscal guardrails. It also points to beel_docs_search for exhaustive rules, covering the absence of an output schema by describing what is returned.

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%, and the schema already thoroughly explains company_id including auth and non-disclosure. The description adds no meaning to the parameter itself, only mentions the request has no body, which is not parameter-specific.

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?

Clearly states the tool ensures the company has a default invoice series for STANDARD, SIMPLIFIED, and CORRECTIVE, and returns the resulting set. The verb 'ensures' and specific resource distinguish it from sibling tools like beel_set_default_series or beel_get_default_series.

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?

Implies usage by stating the request takes no body and repeats change nothing, indicating it is idempotent and can be called to guarantee defaults. It references fiscal guardrails and points to beel_docs_search for exhaustive rules, but does not explicitly contrast with setting a specific series via beel_set_default_series.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/beel-es/beel-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server