Skip to main content
Glama
beel-es

BeeL MCP server

Official
by beel-es

beel_list_series

Read-onlyIdempotent

List invoice series for a company by NIF, filter by active status and document type, and retrieve paginated or full results.

Instructions

Returns the invoice series of a company (NIF), optionally filtered by active and by document_type — a document_type filter always includes the UNASSIGNED series, which are compatible with any type.

Pagination is opt-in here: send page and/or limit to receive a single page plus a data.pagination block with the totals. Omit both and the response carries the full list in data.series and no pagination block.

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

⚠️ 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
pageNoPage number (starts at 1). Omit for the full, unpaginated list.
limitNoItems per page. Omit for the full, unpaginated list.
activeNoFilters by activity: `true` returns only active series, `false` only inactive ones. Omit it and you get **all** the series, active and inactive.
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.
document_typeNoFilter by document type (UNASSIGNED series are always included)
Behavior5/5

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

Beyond the readOnly/openWorld/idempotent hints already in annotations, the description adds rich behavioral detail: pagination response modes (data.series vs data.pagination), the unconditional inclusion of UNASSIGNED series, and the company_id auth behavior (403 for unreachable/non-existent NIFs, no existence disclosure). This goes well beyond the annotations.

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: core purpose first, then pagination behavior, endpoint, and safety warnings. Each sentence adds value given the fiscal complexity, though it is longer than strictly minimal. The front-loading of the purpose and the logical flow justify the length.

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?

Despite lacking an output schema, the description discloses response shape (data.series vs data.pagination with totals), pagination modes, auth context, and points to further docs. It leaves no critical ambiguity for an agent to call the tool correctly.

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?

The input schema already provides complete descriptions for all 5 parameters (100% coverage), including pagination semantics, company_id context, and the UNASSIGNED filter behavior. The description largely reiterates these points without adding new parameter-level meaning, so it meets the baseline for high schema coverage.

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 clearly states a specific verb and resource: 'Returns the invoice series of a company (NIF)', with optional filters named ('active', 'document_type'). It includes the endpoint and even notes the UNASSIGNED inclusion, making it unambiguous and distinct from list operations on other resources.

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 practical usage context: explains opt-in pagination (sending page/limit vs omitting), notes that document_type always includes UNASSIGNED, and points to beel_docs_search for exhaustive rules. It does not explicitly name alternative tools like beel_get_series, but the purpose is specific enough that an agent can select it correctly.

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