Skip to main content
Glama

Use the balance for a number's capture

use_balance_for_capture
Idempotent

After a number's subscription ended, switch its capture to the account's existing balance, as the Payments page in Werify does. Use it only when the user chooses it: from then on, what the number captures draws on that balance as it arrives. The switch itself draws nothing, and a number paused because its subscription ended resumes. Refused while the subscription is still active, when the balance was already chosen, or with no balance to draw on. phone may be omitted when the user has a single number.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "use_balance_for_capture"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneNoThe connected number, from list_connected_numbers. Omit it when the user has a single connected number.

Output Schema

NameRequiredDescriptionDefault
noteNoWhat changed, to tell the user.
phoneNo
resultNoresumed | selected
declinedNoTrue when the confirmation form came back declined.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say the call is non-read-only, non-destructive and idempotent; the description adds non-obvious behavior beyond that — the switch itself draws nothing, a captured number resumes after being paused for an ended subscription, and future captures draw on the balance as they arrive. The refusal conditions also explain how the tool behaves when preconditions fail, which annotations cannot 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 opening sentence front-loads the action, precondition and analogue, and the following sentences layer usage rule, side effects and refusals compactly. The only redundancy is the trailing phone-omission sentence, which restates the schema field description.

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?

With one optional parameter and a published output schema, the description does not need to explain return values; what it must carry — preconditions, refusals, side effects, and the effect on an already-paused number — is all present. Nothing an agent needs to call this correctly is missing.

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 coverage is 100% and the single `phone` parameter is already documented in the schema, including the omit-when-single-number rule. The description's closing sentence repeats that rule rather than adding new meaning (for example, what happens if the number has no subscription history). Baseline 3 applies.

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 and object — switching a number's capture to the account's existing balance — and anchors it to a precise precondition (after the subscription ended) and to a known UI analogue (the Payments page in Werify). An agent can tell exactly what state change this performs, and the subscription-ended scoping separates it from the generic capture-starting siblings.

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 an explicit gating rule ("Use it only when the user chooses it") and enumerates three refusal conditions: subscription still active, balance already chosen, or no balance available. That is a when-to-use plus when-not-to-use plus side-effect consequence, which is as strong as this dimension gets.

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