Skip to main content
Glama
beel-es

BeeL MCP server

Official
by beel-es
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

beel_get_recurring_invoice_history

Read-onlyIdempotent

Retrieve paginated history of invoices generated by a recurring template, showing status and generation dates, newest first. Use pagination to browse older entries.

Instructions

Returns the invoices previously generated from this recurring template, including their status and generation dates, newest first.

Paginated with the usual page/limit, and the usual defaults: without them you get the 20 most recent generations, not the whole history — which grows with every cycle the template runs. Read data.pagination to walk the rest.

The deprecated flat alias GET /v1/recurring-invoices/{recurring_invoice_id}/history does not paginate: it is frozen as it shipped until its Sunset date, and returns the whole history with no pagination. Only this route pages.

Endpoint: GET /v1/companies/{company_id}/recurring-invoices/{recurring_invoice_id}/history

⚠️ Fiscal guardrails — read before calling:

  • How BeeL derives the AEAT invoice type, and the rules each type imposes. (resource: beel://guardrails/invoice-types)

  • What regime_key means, where it lives, and which combinations are rejected. (resource: beel://guardrails/regime-keys)

For the exhaustive rules and worked examples, call beel_docs_search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number, starting at 1. The response echoes it back as `pagination.current_page`.
limitNoHow many items to return per page. The response echoes it back as `pagination.items_per_page`.
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.
recurring_invoice_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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."
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 20,
+  "description": "How many items to return per page. The response echoes it back as `pagination.items_per_page`.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / page
      Added value: +{
+  "default": 1,
+  "description": "Page number, starting at 1. The response echoes it back as `pagination.current_page`.",
+  "minimum": 1,
+  "type": "integer"
+}
  2. First observedv0.3.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description adds value by disclosing pagination defaults, data.pagination walking, newest-first ordering, and the frozen deprecated alias behavior. It also surfaces fiscal guardrail resources, which goes well beyond the structured 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 description is front-loaded with the core purpose, then uses bolded warnings, a deprecated-alias note, and a compact guardrail bullet list. Every section adds operational value, including the endpoint, pagination caveats, and pointers to additional docs. It is detailed but well-structured and not padded.

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?

Given the moderate complexity, rich annotations, and high schema coverage, the description fills the important gaps: return content, ordering, pagination defaults, deprecated alias behavior, and fiscal guardrails. Even without an output schema, an agent has enough to call the tool correctly and interpret the response shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already covers 75% of parameters in detail, including company_id semantics and page/limit defaults. The description adds behavioral meaning by explaining that omitting pagination yields only the 20 most recent generations and that data.pagination must be read to walk further. This is a useful complement to the schema without redundant repetition.

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 opens with a specific verb and resource: 'Returns the invoices previously generated from this recurring template, including their status and generation dates, newest first.' This clearly distinguishes the tool from sibling tools like beel_get_recurring_invoice or beel_list_recurring_invoices, and the endpoint line reinforces the exact scope.

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 strong usage guidance around pagination: omitting page/limit returns only the 20 most recent generations, and it explicitly contrasts the deprecated flat alias that does not paginate. It does not explicitly name sibling alternatives for viewing the recurring template itself, but the pagination and alias distinction makes the intended use 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