Capable

Change company billing state

manage_company_billing

DestructiveIdempotent

Activate a company, or request human approval for activation, after reviewing get_company_billing. Supply the exact quoted revision and price in the returned billing currency’s minor units (cents or öre); never guess them. AI/API activation additionally needs an administrator-granted automation budget even for workspace admins. Without that authority this creates a pending human approval request and does not activate or purchase capacity. Archive and restore require an authorized person to confirm in the company's web panel; this tool cannot perform them. Never invoke this merely to read, enrich, import or qualify a company. Annual capacity purchases are a separate billing-admin action.

When to use: Explicitly activate a reviewed company within an administrator-approved automation budget, or request human approval. Archive and restore require the company's web panel.

Example: Activate this company using the reviewed price, or request approval if needed.

Input Schema

Name	Required	Description
`action`	Yes	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.
`account_id`	Yes	The account (company) id to change — the same uuid you passed to get_company_billing for the quote you are acting on.
`idempotency_key`	Yes	Keep this same key when retrying the same approved action.
`expected_revision`	Yes	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.
`approved_price_minor`	Yes	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.

Output Schema

Name	Required	Description	Default
`state`	No
`account`	No
`revision`	No
`requestId`	No
`approvalUrl`	No
`workingCount`	No
`approvalRequired`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026
- removedInput schema / $schema
```
Removed value: -"https://json-schema.org/draft/2020-12/schema"
```

Changed1 schema field changedOct 20, 2026

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)$"

Changed4 schema fields changedOct 19, 2026

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)$"

Changed1 schema field changedOct 6, 2026

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."

First observedOct 6, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare destructive/idempotent/openWorld/non-readOnly, but the description goes well beyond them: it discloses the administrator-granted automation budget requirement, that the fallback is a pending human approval rather than an activation or capacity purchase, that live-price/revision drift causes refusal, and that archive/restore can only happen in the web panel.

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 and constraints are front-loaded, and the sentences carry real information. It loses a point for mild redundancy, since the archive/restore web-panel constraint is stated in the opening paragraph, repeated in 'When to use', and echoed by the example.

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?

An output schema exists so return values need not be explained, and the description covers everything else an agent needs: the quote prerequisite, the exact-value requirement, the automation-budget precondition, the approval fallback, and the actions this tool cannot perform.

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 operational meaning on top: it tells the agent to never guess the revision and price, to supply them in the billing currency's minor units (cents or öre), and to reuse the idempotency key on retries. This reinforces the most failure-prone inputs rather than merely restating the schema.

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 set (activate or request human approval for activation) and resource (company billing state), and names the sibling it depends on (get_company_billing). It also explicitly carves out what the tool cannot do (archive/restore), so an agent can distinguish it from neighbors without opening any schema.

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?

Includes an explicit 'When to use' line, names the prerequisite read tool, states the alternative path for archive/restore, and gives clear exclusions ('Never invoke this merely to read, enrich, import or qualify a company'). Nothing about routing is left to inference.

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

All Capable tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?