Skip to main content
Glama

Buy Capacity Channels

buy_capacity_channels
Destructive

Purchase additional channels into one of the customer's Capacity Pools by creating an Order. Provide the capacity_pool_id (from list_capacity_pools) and qty — the number of channels to add to the pool. The price is prorated to the pool's renew date. Charges the customer's balance; the channels are added to the pool immediately and can then be distributed across Shared Capacity Groups or dedicated-channel reservations. A DID can only draw channels from a pool that covers its country — pass the optional country_iso to fail fast on a mismatched pool before any money is spent. All amounts are in USD. This spends real money.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qtyYesNumber of channels to purchase into the pool.
country_isoNoOptional pre-check: ISO 3166-1 alpha-2 country code of the DIDs this capacity is for. The purchase fails BEFORE any confirmation/charge if the pool does not cover that country (a DID can only draw channels from a pool covering its country — see covered_country_isos in list_capacity_pools).
capacity_pool_idYesUUID of the Capacity Pool to buy channels into (from list_capacity_pools).
confirmation_tokenNoLeave empty on the first call — the tool returns a confirmation_token + preview and charges nothing. Re-call with that confirmation_token to execute the purchase. If the confirming call's response is lost, it is safe to retry with the SAME confirmation_token — a repeat returns the original result and never purchases twice.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior5/5

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

Far exceeds the annotations (which only flag non-readOnly, destructive, non-idempotent): it discloses prorated pricing to the renew date, immediate balance charge, immediate channel availability, and the confirmation_token preview-then-execute flow with safe retry semantics. 'This spends real money' makes the financial consequence unmistakable.

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?

Front-loaded with the core action, then layers pricing, delivery, and pre-check details in order. It is somewhat long, but nearly every sentence carries actionable information for a money-spending operation.

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, irreversible money-spending tool with no output schema, the description covers prerequisites, preview/confirm flow, retry safety, and downstream usage of purchased channels. An agent has everything needed to call it correctly without accidental double purchases.

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; the description adds value beyond the schema by explaining why country_iso exists (fail fast before any charge) and reinforcing the capacity_pool_id source. The confirmation_token two-call semantics are covered richly in the description, though mostly duplicating the schema text.

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?

States a specific verb (purchase/add channels) and resource (Capacity Pools via an Order), and distinguishes itself from siblings like buy_did and list_capacity_pools. An agent immediately understands this is a capacity-purchase operation.

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?

Provides clear context: the pool_id comes from list_capacity_pools, qty is the number to add, and country_iso is an optional fail-fast pre-check for mismatched pools. It does not explicitly name alternatives or exclusions, but the workflow and preconditions are well-telegraphed.

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