Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_skip_recurring_invoice

DestructiveIdempotent

Skips the next scheduled invoice generation for a recurring invoice and advances its generation date to the following period, issuing nothing.

Instructions

Skips the next scheduled invoice generation and advances the generation date to the following period. Nothing is issued.

BeeL API endpoint: POST /v1/companies/{company_id}/recurring-invoices/{recurring_invoice_id}/skip (reference: https://docs.beel.es)

⚠️ Read before calling:

  • Fiscal rules, domains simplified, taxes: beel_rules_list with domain, or resource beel://guardrails/.

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>",
      "recurring_invoice_id": "<recurring_invoice_id>"
    },
    "name": "beel_skip_recurring_invoice"
  }
}

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.
idempotency_keyNoOptional idempotency key for this operation. Omit it and one is derived from the request itself, which makes a blind retry safe but also collapses a SECOND, deliberately identical operation into the first for 24 hours. Set it — to an order id, or anything unique per intended operation — whenever you mean to create something that may look identical to what you just created.
recurring_invoice_idYesUnique identifier (UUID) of the recurring invoice template, as returned when it is created or listed. A template of another company answers `404` with `RECURRING_NOT_FOUND`, exactly like one that does not exist.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • addedInput schema / properties / recurring_invoice_id / description
      Added value: +"Unique identifier (UUID) of the recurring invoice template, as returned when it is created or listed. A template of another company answers `404` with `RECURRING_NOT_FOUND`, exactly like one that does not exist."
  2. 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."
  3. First observedv0.3.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false; the description adds the crucial semantic that despite the mutation nothing is issued and the schedule simply advances, which is exactly the context an agent needs to avoid alarming a user. It also names the underlying endpoint. It stops short of stating reversibility (can the skip be undone?) or behavior when the template is already skipped.

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 decisive information is front-loaded in the first sentence, followed by the endpoint reference and a clearly delimited warning block. The repeated 'BeeL API endpoint / docs.beel.es' line is somewhat boilerplate but short and useful for lookup, so little is wasted.

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?

For a two-required-parameter mutation with no output schema, the description covers the action, the resulting state change, the absence of an issued invoice, and a compliance prerequisite. The main omissions are the response/return shape (since no output schema exists) and edge cases such as skipping an already-skipped or cancelled template.

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%, so company_id, recurring_invoice_id and idempotency_key are fully documented with error semantics (403, RECURRING_NOT_FOUND) in the schema itself. The description adds no meaning beyond that except the endpoint path implying company_id and recurring_invoice_id are path parameters. Baseline 3 applies.

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 opening sentence gives a specific verb (skip), a specific resource (the next scheduled invoice generation), and the concrete state change (generation date advances to the following period). 'Nothing is issued' preempts the obvious confusion with the sibling beel_generate_recurring_invoice_now and with beel_set_recurring_invoice_status, so an agent can separate them without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is a pre-call directive ('Read before calling') pointing to beel_rules_list with a domain and the beel://guardrails resource, which is genuine prerequisite guidance. However, it never states when to choose skip versus pausing/setting status on the template (beel_set_recurring_invoice_status) or generating immediately, and gives no 'when not to use' condition. Usage is implied by the effect rather than selected explicitly.

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