Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_deactivate_company

DestructiveIdempotent

Switch off a company in a chosen TEST or PROD mode while preserving activation history; Live shutdowns are scheduled for billing-cycle end, and TEST or enterprise PROD changes apply immediately.

Instructions

Switches the company off in the mode given by environment; the other mode is untouched.

  • Sealed, not deleted: the activation's history survives. After the switch-off takes effect the NIF can neither issue nor correct invoices in that mode until it is switched on again, and in Live that sealing is what releases the NIF for another account.

When it takes effect

  • In Live the switch-off is scheduled, not immediate: the cycle is paid up front, so the response carries an effective_at and the NIF keeps invoicing until then. Nothing is refunded. effective_at is the end of the current billing cycle, unless the NIF was switched on within that same cycle, in which case it is the end of the next one.

  • TEST, and PROD under an enterprise contract: immediate, and answer with no effective_at.

Repeats and permissions

  • Repeating the call: on a mode whose switch-off is already pending it returns the same date with already_scheduled: true; switching off a mode that was never on is a silent no-op.

  • Permission: switching off in Live requires being the billing subject of the account.

BeeL API endpoint: DELETE /v1/companies/{company_id}/activations (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>",
      "environment": "<environment>"
    },
    "name": "beel_deactivate_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
company_idYesUnique identifier (UUID) of the company being switched 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.
environmentYesMode to switch the NIF off in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.10.0
    • addedInput schema / properties / environment / type
      Added value: +"string"
  2. Addedv0.5.0

TDQS

A4.6/5.0
Behavior5/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, but the description goes well beyond them: it explains that data is sealed rather than removed, that invoices can be neither issued nor corrected until reactivation, that Live sealing releases the NIF for another account, that nothing is refunded, that `effective_at` is returned, and that a repeat call yields `already_scheduled: true` while switching off a never-activated mode is a silent no-op. It also discloses the billing-subject permission requirement.

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?

Content is front-loaded with the core action followed by clearly headed sections for timing, repeats and permissions, so the agent can scan to the relevant part. It is on the long side and restates the mode-scoping idea in both the opening and the 'Sealed' bullet, but every paragraph carries operational information.

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?

There is no output schema, yet the description names the response fields the agent will encounter (`effective_at`, `already_scheduled`) and explains when each appears. Combined with timing, idempotency and permission semantics, a caller has everything needed to invoke this mutation and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning to `environment` by stating the switch-off applies only to that mode and leaves the twin untouched, which the schema's one-line 'Mode to switch the NIF off in' does not convey. The `company_id` permission behaviour (403 on unreachable or nonexistent companies) is already covered in the schema, so no extra credit there.

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 description opens with a specific verb and resource, 'Switches the company off in the mode given by `environment`', and immediately scopes it: the other mode is untouched. The phrase 'Sealed, not deleted' implicitly separates it from the destructive sibling `beel_delete_company` and mirrors `beel_activate_company`, so an agent can place it without opening the schema.

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?

It gives clear conditions for use: what happens in Live versus TEST/PROD-under-enterprise, that the Live switch-off is scheduled rather than immediate, what happens on repeat calls, and that Live requires being the billing subject. It stops short of explicitly naming the alternative tools (e.g. `beel_delete_company` for true deletion, `beel_activate_company` to reverse), which keeps it from a 5.

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