Skip to main content
Glama
beel-es

BeeL MCP server

Official
by beel-es
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

beel_get_default_series

Read-onlyIdempotent

Check whether a company's automatic invoicing document types have a default invoice series, returning the series ID when set. Detects missing defaults that make automatic flows skip, so you can assign one before issuing.

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.

Endpoint: GET /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_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
Behavior5/5

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

Annotations already mark it read-only and idempotent, and the description adds meaningful behavior: no pagination, no page/limit, the full set is always returned, environment is resolved from context, and what 'no default' means operationally. The fiscal guardrail pointer also warns the caller of important numbering constraints beyond the structured metadata.

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?

The description is well-structured with a purpose sentence, bullets, and a guardrail callout. Minor redundancy exists — 'it takes no input' appears twice, and the endpoint line is helpful but not strictly necessary — but the overall organization is efficient and front-loaded.

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?

With one parameter, a rich schema, and strong annotations, the description covers everything needed: response contents, collection semantics, absence of pagination, environment behavior, and relevant fiscal context. The pointer to `beel_docs_search` fills any need for exhaustive detail without burdening the description.

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 explains that `company_id` is a UUID, not a NIF, and carries auth semantics such as 403 behavior. The description does not add parameter-level meaning and even loosely refers to 'company (NIF)', which is slightly at odds with the schema's explicit 'not its NIF' clarification, though not enough to constitute a contradiction.

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 clearly states a specific verb ('Reports') and resource (default invoice series per `DocumentType`), and explains the response shape (`exists`, `series_id`). It does not explicitly name sibling tools like `beel_get_series` or `beel_set_default_series` to distinguish itself, so it misses the top bar for sibling differentiation.

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?

The description gives clear context: this is for automatic invoicing flows, returns all defaults in a bounded collection, and requires no input beyond the company. It does not explicitly state when to prefer this over siblings or when not to use it, but the domain and closed-catalogue behavior make the usage context clear.

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