Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_delete_invoice_schedule

DestructiveIdempotent

Removes an invoice schedule, returning it to a plain draft; repeat calls are idempotent and return 204 even if no schedule exists.

Instructions

Removes the scheduling of an invoice, returning it to a plain draft. Idempotent: an invoice that is not scheduled answers 204 all the same. Unlike the PUT, it does not require the scheduled_invoices feature.

BeeL API endpoint: DELETE /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_delete_invoice_schedule"
  }
}

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.
invoice_idYesInvoice ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.10.0
    • addedInput schema / properties / invoice_id / type
      Added value: +"string"
  2. Changed3 schema fields changedv0.5.0
    • 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."
  3. First observedv0.3.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description still adds real value: it clarifies that only the schedule is destroyed (the invoice survives as a draft), specifies the 204 response for an unscheduled invoice, and notes the feature-flag independence. It stops short of covering authorization requirements or whether the prior schedule details are recoverable.

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 effect and idempotency semantics are front-loaded in two tight sentences, which is the right ordering. The trailing guardrail block is longer than the substantive content, and its second bullet is a sentence fragment ('The status names, the proforma lifecycle, and which tool performs each operation') that conveys little on its own.

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-parameter destructive mutation with no output schema, the description covers the essential unknowns: what is removed, what remains, idempotent responses, and a pointer to the invoice state machine. Authorization/scopes and any side effects on related records are left unaddressed.

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 company_id field already explains UUID-vs-NIF, header independence, and the 403 behaviour for foreign or nonexistent companies. The description adds nothing further about the two parameters, so the baseline 3 applies.

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?

States a specific verb and resource plus the concrete outcome: the schedule is removed and the invoice returns to a plain draft, which distinguishes it from deleting the invoice itself. The contrast with the sibling that sets a schedule is made obliquely as 'the `PUT`' rather than by naming beel_set_invoice_schedule or beel_patch_invoice_schedule.

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?

Usage is implied through the stated effects and the note that this call, unlike the PUT, does not require the `scheduled_invoices` feature, which helps an agent choose between the two. However, there is no explicit when-to-use/when-not-to-use statement naming the sibling tools, and the '⚠️ Read before calling' block points at guardrail resources without saying under what conditions this tool should be avoided.

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