Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_cancel_representation

DestructiveIdempotent

Cancels a company's active AEAT representation, preventing production invoice submissions until a new representation document is generated and signed.

Instructions

Cancels the active AEAT representation of a company.

  • Effect: until a new document is generated and signed, the company can no longer submit invoices to AEAT in production. Its activation and its ability to issue non-VeriFactu invoices are untouched.

  • No active representation: rejected with 400. Cancelling is a state transition, not a delete-if-present.

BeeL API endpoint: DELETE /v1/companies/{company_id}/representation (reference: https://docs.beel.es)

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

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. First observedv0.3.1

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description still adds real context beyond them: what actually breaks (production AEAT invoice submission), what is explicitly untouched (company activation and non-VeriFactu issuing), and the 400 failure mode. Minor tension worth noting: a repeat call on an already-cancelled representation errors rather than succeeding, which is idempotency of state rather than of response, and the description could say so more directly.

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 lead sentence is front-loaded and the two bolded bullets make effect and failure mode scannable at a glance. The trailing "BeeL API endpoint /docs" line is reference material rather than invocation guidance, so it is slightly surplus, but nothing is genuinely wasteful.

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 single-parameter destructive mutation with no output schema, the description covers the operational consequence, the untouched surfaces, and the error case, with annotations carrying the safety flags. What is left thin is recovery: it does not tell the agent which tool regenerates the representation or what the caller must do to restore production issuing.

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?

There is a single parameter and schema description coverage is 100%; the schema already explains that company_id is a UUID, is not the NIF, and is the sole source of context including the 403 behaviour for unreachable companies. The description contributes nothing further about the parameter, 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?

"Cancels the active AEAT representation of a company" gives a specific verb plus a specific resource, which separates it from beel_generate_representation, beel_get_representation and beel_download_representation_document that share the same domain. It stops short of naming those siblings explicitly, so the differentiation rests on the verb rather than on an explicit contrast.

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?

The description supplies one concrete precondition: with no active representation the call is rejected with 400, framed as "a state transition, not a delete-if-present". That is useful when-not guidance, but it never states when an agent should reach for this tool instead of the sibling representation tools (generate / get / download) or what path restores the revoked state beyond the vague "until a new document is generated and signed".

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