Skip to main content
Glama

Change company billing state

manage_company_billing
DestructiveIdempotent

Changes a company's billing state. activate: active account at the revision and price get_company_billing quoted (minor units, never guessed); without an admin-granted automation budget, admins included, it files a pending human approval and buys nothing. archive: only with confirm:true after the person's explicit yes in this conversation; history stays, and it stops the company's active-account charge from the next end-of-day count, or frees a prepaid place on annual billing. keep: the person still works with a quiet company; it stays active. Archive and keep need an admin or billing permission. Never call this to read, enrich, import or qualify a company.

When to use: The person asks to activate a reviewed company, or answers whether they still work with a quiet one.

Example: We stopped working with Halden & Co. Archive it.

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": {
      "account_id": "<account_id>",
      "action": "<action>"
    },
    "name": "manage_company_billing"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesrestore is web-only.
confirmNoarchive: true only once the person said yes to archiving this company.
account_idYesThe company's uuid, as passed to get_company_billing.
idempotency_keyNoactivate and archive: reuse it when retrying the same action.
expected_revisionNoactivate and archive: the reviewed `revision`; refused once usage changed.
approved_price_minorNoactivate: the reviewed `activationPriceMinor` (cents or öre); refused if the live price differs.

Output Schema

NameRequiredDescriptionDefault
stateNo
keptAtNo
accountNo
revisionNo
requestIdNo
approvalUrlNo
workingCountNo
approvalRequiredNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • changedInput schema / properties / account_id / description
      Previous value: -"The account (company) id to change — the same uuid you passed to get_company_billing for the quote you are acting on."New value: +"The company's uuid, as passed to get_company_billing."
    • changedInput schema / properties / action / description
      Previous value: -"activate makes the company a paid active account or creates a pending human approval request. archive and restore cannot be performed by this tool; an authorized person must confirm them in the company's web panel."New value: +"restore is web-only."
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "activate",
      -  "archive",
      -  "restore"
      -]New value: +[
      +  "activate",
      +  "archive",
      +  "keep",
      +  "restore"
      +]
    • changedInput schema / properties / approved_price_minor / description
      Previous value: -"The reviewed `activationPriceMinor` from get_company_billing, in the billing currency's minor units (cents or öre); activate is refused when the live price differs."New value: +"activate: the reviewed `activationPriceMinor` (cents or öre); refused if the live price differs."
    • addedInput schema / properties / confirm
      Added value: +{
      +  "description": "archive: true only once the person said yes to archiving this company.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / expected_revision / description
      Previous value: -"The `revision` from the get_company_billing result you reviewed; if the workspace's account usage changed since, the action is refused and needs a fresh quote."New value: +"activate and archive: the reviewed `revision`; refused once usage changed."
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"Keep this same key when retrying the same approved action."New value: +"activate and archive: reuse it when retrying the same action."
    • changedInput schema / required
      Previous value: -[
      -  "account_id",
      -  "action",
      -  "expected_revision",
      -  "approved_price_minor",
      -  "idempotency_key"
      -]New value: +[
      +  "account_id",
      +  "action"
      +]
    • addedOutput schema / properties / keptAt
      Added value: +{
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  3. Changed1 schema field changed
    • removedInput schema / properties / account_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  4. Changed4 schema fields changed
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / account / additionalProperties
      Removed value: -false
    • removedOutput schema / properties / account / properties / id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  5. Changed1 schema field changed
    • changedInput schema / properties / action / description
      Previous value: -"activate (paid active account, or a pending approval), archive (stops paid usage, keeps history) or restore (a deleted company returns as prospect/archived, never active)."New value: +"activate makes the company a paid active account or creates a pending human approval request. archive and restore cannot be performed by this tool; an authorized person must confirm them in the company's web panel."
  6. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already mark the tool as destructive and idempotent, but the description adds substantial behavioral context: archive preserves history and stops charges, activate without an automation budget files a pending human approval and buys nothing, and both archive and keep need admin or billing permission.

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 description is front-loaded with the core action semantics and then gives usage guidance and an example. It is dense but mostly earns its length for a multi-action destructive tool, though some clauses are verbose.

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 complex destructive billing mutation with an output schema and annotations, the description covers the available actions, prerequisites, side effects, confirmation requirements, permissions, and misuse boundaries. An agent has enough context to call it correctly.

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%, so the schema already documents all six parameters. The description contextualizes activate's revision/price and archive's confirm requirement, but it largely mirrors the schema's parameter descriptions rather than adding new syntax or format details.

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 states a specific verb/resource: it changes a company's billing state, and it enumerates activate, archive, and keep. It also distinguishes the tool from get_company_billing and explicitly rules out read/enrich/import/qualify usage.

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?

It gives explicit triggers: the person asks to activate a reviewed company or answers whether they still work with a quiet one. It also specifies when not to use the tool and adds action-specific conditions such as archive requiring confirm:true after an explicit yes.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources