Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_activate_company

DestructiveIdempotent

Activates an existing company in an explicit TEST or PROD mode, handling Live checkout and billing while cancelling pending switch-offs without duplicate charges.

Instructions

Switches an existing company on in the mode carried in the body. The mode is always explicit and never taken from the credential's environment, so a Test key can switch a NIF on in Live.

Modes and billing

  • TEST: immediate and free.

  • PROD: immediate when the account already has a card on file or an enterprise contract, and the NIF is added to the existing subscription. With no card on file it answers 402 CHECKOUT_REQUIRED, returning a checkout_url when success_url and cancel_url are supplied. It also requires being the billing subject of the account (403 NOT_BILLING_OWNER otherwise).

  • billing_period: picks the plan the checkout sells — MONTHLY (default) or ANNUAL. It only matters when a checkout is opened. Accounts with a negotiated rate or an enterprise contract cannot buy the annual plan (422 ANNUAL_PLAN_NOT_AVAILABLE).

Idempotency and pending switch-offs

  • Repeating the call: opens no second checkout and adds no second subscription item; it returns the existing activation with already_active: true. The same Idempotency-Key sent to this route and to the nested one it replaces is the same operation, so it is replayed and never charged twice.

  • A pending switch-off is cancelled: while it is pending the NIF is still on — it just carries an effective date — so switching it on again only removes that date, answers scheduled_deactivation_cancelled: true, and charges or credits nothing. It does commit the NIF to the next billing cycle, though, so under an agreement capped at a number of Live NIFs it asks for a seat like a new NIF would, and is rejected with 409 NIF_LIMIT_REACHED when the cap is already full.

BeeL API endpoint: POST /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>",
      "body": "<body>"
    },
    "name": "beel_activate_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
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.
idempotency_keyNoOptional idempotency key for this operation. Omit it and one is derived from the request itself, which makes a blind retry safe but also collapses a SECOND, deliberately identical operation into the first for 24 hours. Set it — to an order id, or anything unique per intended operation — whenever you mean to create something that may look identical to what you just created.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.10.0
    • addedInput schema / $defs / ActivateCompanyRequest / properties / billing_period
      Added value: +{
      +  "allOf": [
      +    {
      +      "$ref": "#/$defs/BillingPeriod"
      +    }
      +  ],
      +  "description": "Billing period of the plan bought when switching on in Live opens a checkout. `ANNUAL` charges the yearly per-NIF price up front, with no overage item in the checkout; `MONTHLY` is the monthly per-NIF price plus overage. Only read when a checkout is opened. Defaults to `MONTHLY` when omitted."
      +}
    • addedInput schema / $defs / BillingPeriod
      Added value: +{
      +  "description": "Nominal billing period of a subscription.",
      +  "enum": [
      +    "MONTHLY",
      +    "ANNUAL"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / body / type
      Added value: +"object"
  2. Addedv0.5.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true, readOnlyHint=false), the description discloses what actually happens: 402 CHECKOUT_REQUIRED with checkout_url, 409 NIF_LIMIT_REACHED, 403 NOT_BILLING_OWNER, charge/credit behavior, and the fact that a pending switch-off commits the NIF to the next billing cycle. It also explains idempotent replay across the route and its nested predecessor, which the annotations alone could not convey.

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 core purpose is front-loaded in the first sentence, and the remainder is organized under clear headers (Modes and billing, Idempotency and pending switch-offs). It is long, but nearly every line carries operational information; a few billing-edge sentences are dense but not wasteful.

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 mutation tool with nested body, no output schema, and monetary side effects, the description is unusually complete: it covers modes, billing prerequisites, idempotent retry semantics, pending-switch-off interactions, and the specific error codes an agent may need to handle. Nothing material required to call it correctly is missing.

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?

At 67% schema coverage the description adds real meaning: it explains that environment is always taken from the body (not credentials), that billing_period only matters when a checkout is opened (default MONTHLY), and that repeating a call opens no second checkout. The idempotency_key consequences are also spelled out, compensating for the partial schema coverage.

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?

The first sentence gives a specific verb and resource ("Switches an existing company on in the mode carried in the body") and immediately clarifies that the mode is explicit rather than inherited from credentials. This is precise enough to distinguish it from beel_deactivate_company, though it never names that sibling explicitly to confirm the relationship.

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?

The Modes and billing section explains in detail when each mode applies, when a checkout opens (no card on file), and which errors (403 NOT_BILLING_OWNER, 422 ANNUAL_PLAN_NOT_AVAILABLE) gate the call. It stops short of explicitly contrasting with alternative tools like beel_deactivate_company or beel_provision_account, but the operational conditions are exhaustive.

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