BeeL MCP server

Official

Overview Schema Source Related Servers Discussions Admin

beel_get_invoice_schedule

Read-onlyIdempotent

Retrieves the date and generation mode currently scheduled for an invoice, returning 404 when no schedule exists, so you can read the mode before updating only the date.

Instructions

Returns the date and generation mode currently scheduled for this invoice. An invoice with no scheduling answers 404, since the sub-resource does not exist yet. To move only the date, read the current generation_mode here and send it back on the PUT.

BeeL API endpoint: GET /v1/companies/{company_id}/invoices/{invoice_id}/schedule (reference: https://docs.beel.es)

⚠️ Read before calling:

Fiscal rules, domains lifecycle, void, corrective: beel_rules_list with domain, or resource beel://guardrails/.
The status names, the proforma lifecycle, and which tool performs each operation. (resource: beel://guardrails/invoice-state-machine)

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>",
      "invoice_id": "<invoice_id>"
    },
    "name": "beel_get_invoice_schedule"
  }
}

Input Schema

Name	Required	Description	Default
`company_id`	Yes	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.
`invoice_id`	Yes	Invoice ID

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.10.0Nov 5, 2026
- addedInput schema / properties / invoice_id / type
```
Added value: +"string"
```

Changed3 schema fields changedv0.5.0Aug 30, 2026

removedInput schema / $defs / UUID / example

Removed value: -"550e8400-e29b-41d4-a716-446655440000"

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

First observedv0.3.1Aug 25, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: the 404 response when the sub-resource does not exist yet, and the coupling between this read and the subsequent PUT.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first three sentences are tight and front-loaded with purpose, error behavior, and the write workflow. The trailing '⚠️ Read before calling' block is largely generic boilerplate about fiscal rules and the invoice state machine that is only weakly relevant to a read-only schedule getter, diluting the signal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 must carry the return shape; it names the two returned fields (date, generation_mode) but not their format or the possible generation_mode values, which matters for the documented 'send it back on the PUT' workflow. It is adequate but leaves a real gap for a caller that must echo the value back.

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 both required parameters (company_id, invoice_id) are documented in the schema, including 403 semantics for company_id. The description adds no parameter-level meaning, so the 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?

States a specific verb and resource: 'Returns the date and generation mode currently scheduled for this invoice.' This cleanly separates it from beel_get_invoice (full invoice), beel_set_invoice_schedule and beel_patch_invoice_schedule (mutations of the same sub-resource).

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?

Gives a concrete usage rule: read generation_mode here and send it back on the PUT when only moving the date, plus the 404 condition when no schedule exists. It never names the sibling tools (beel_set_invoice_schedule / beel_patch_invoice_schedule) or states when not to use this, so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server