Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_delete_company

DestructiveIdempotent

Deletes a company from the account so it stops appearing and being billed; existing invoices are retained, and removal may be blocked by active Live NIFs, Live invoices, or primary NIF.

Instructions

Removes a company from the account: it stops appearing and stops being billed.

  • Existing invoices: those already issued are retained, but the company-scoped API can no longer resolve them once the NIF is removed.

  • What blocks removal: a NIF activated in Live (409 COMPANY_ACTIVE_IN_PRODUCTION), one holding any invoice in Live — issued, draft or proforma (409 COMPANY_HAS_INVOICES) — and the account's primary NIF (400 CANNOT_DELETE_PRIMARY).

  • Deactivating first: switching off in Live is scheduled to the end of the paid cycle, so the removal only becomes possible once that takes effect.

  • Test: NIFs never activated, or activated only in Test, are removed right away, and invoices in Test never block.

  • Idempotency-Key: without one, a retry after a timeout answers 403 instead of the original 204.

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

⚠️ Read before calling:

  • Which company an operation acts on, and how that is selected. (resource: beel://guardrails/multi-nif)

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_delete_company"
  }
}

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. Addedv0.5.0

TDQS

A4.4/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, but the description adds materially more: invoice retention after NIF removal, the primary-NIF guard, Test-vs-Live blocking differences, and the 403-instead-of-204 retry answer without an Idempotency-Key. The last point slightly qualifies the idempotentHint by exposing a retry failure mode, but it refines rather than contradicts it, so no contradiction is flagged; missing only a statement of required scopes/permissions.

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 states the effect up front and the bulleted blockers make scanning easy; every bullet conveys actionable information. It is on the long side and the guardrails warning is somewhat boilerplate, keeping it just short of a 5.

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?

For a destructive single-parameter mutation with no output schema, the description covers side effects, blocking error codes, timing of deactivation-driven removal, and retry semantics, plus an endpoint reference and API docs link. An agent could call this correctly and predict the failure modes without opening anything else.

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 description already covers UUID format, account derivation, header irrelevance, and 403 nondisclosure, so the schema carries the parameter burden. The tool description itself adds little parameter-level meaning beyond mentioning that the company-scoped API can no longer resolve invoices once the NIF is removed, and points to beel://guardrails/multi-nif for selection rules.

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?

"Removes a company from the account: it stops appearing and stops being billed" gives a specific verb, resource, and observable consequence. It also implicitly separates itself from the sibling beel_deactivate_company by explaining that deactivation is a precondition rather than an equivalent action.

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

Usage Guidelines5/5

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

The description names the exact conditions that block the call (409 COMPANY_ACTIVE_IN_PRODUCTION, 409 COMPANY_HAS_INVOICES, 400 CANNOT_DELETE_PRIMARY) and explains the alternative path via deactivation being scheduled to end of paid cycle. Test vs Live divergence is called out explicitly, which is precisely the when/when-not guidance an agent needs.

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