Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_get_default_series

Read-onlyIdempotent

Checks, for each invoice document type, whether the company has a default series and returns its series_id, so automatic invoicing flows know when an explicit series is required.

Instructions

Reports, for each DocumentType used by automatic invoicing flows, whether the company (NIF) has a default invoice series and which one: exists, plus the series_id when there is one.

  • No default: that document type cannot be issued without naming a series_id explicitly, and automatic flows skip it with failure.payment.skip.missing_default_series.

  • Environment: resolved from the request context; it takes no input.

Closed catalogue. This collection is fixed and bounded — one entry per DocumentType: it carries no pagination, it takes no page/limit, and every response holds the whole set.

BeeL API endpoint: GET /v1/companies/{company_id}/series/defaults (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>"
    },
    "name": "beel_get_default_series"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • 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."
  2. First observedv0.3.1

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, it discloses that the collection is fixed and bounded, that there is no `page`/`limit` and every response holds the whole set, and that environment is resolved from request context. That is real behavioral value the annotations cannot convey. It stops short of describing the shape of an entry or error responses beyond what the schema covers.

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 statement, then bolded subsections for no-default behavior, environment, and catalogue shape, followed by a short pre-call pointer block. The guardrails/pointer section at the end is somewhat verbose and not essential to invoking the tool, which keeps it from a 5.

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 necessary work by naming the response fields (`exists`, `series_id`), stating the entry granularity, and noting there is no pagination wrapper. Combined with a fully documented single parameter and complete annotations, an agent has enough to call it correctly; only the exact JSON envelope is left implicit.

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 100% and the `company_id` property description is already richer than the tool description (UUID, 403 behavior, header independence), so the baseline of 3 applies. The line 'Environment: resolved from the request context; it takes no input' is slightly at odds with the required `company_id` and may momentarily confuse an agent about whether it must supply a company.

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?

The description names a precise verb and resource: report per `DocumentType` whether a default invoice series exists and which `series_id` it is. It also scopes itself explicitly ('one entry per `DocumentType`', closed catalogue, no pagination), which separates it from the listing siblings such as beel_list_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?

It explains the operational consequence of a result ('No default: that document type cannot be issued without naming a `series_id` explicitly, and automatic flows skip it with `failure.payment.skip.missing_default_series`'), which tells an agent when this check matters before issuing. It does not explicitly name alternatives (beel_list_series, beel_set_default_series, beel_ensure_default_series could be confused), so it stops short of full when/when-not routing.

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