phone_buy_numberProvision a real phone number (SMS + voice) for your agent. Costs 3.00 USDC, paid per-action via x402.
| Name | Required | Description | Default |
|---|---|---|---|
| country | Yes | ISO-2 country code, e.g. 'US' | |
| payment | No | base64 x402 payment payload (X-PAYMENT); omit on first call to receive payment instructions | |
| areaCode | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses the cost (3.00 USDC) and payment method (x402 per-action), which are important behavioral traits. However, it does not explain the payment flow (e.g., initial call without payment), eventual number lifecycle, or any other side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the main action and cost. Every word contributes, with no fluff or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool involves a payment flow (schema notes 'omit on first call to receive payment instructions') and no output schema, but the description omits this procedural detail and does not indicate what the response contains. For a 3-parameter purchase tool with no annotations, this is inadequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema covers country and payment with descriptions, but areaCode lacks a description. The tool description does not add any parameter-level meaning, failing to compensate for the missing areaCode semantics. Schema coverage is 67%, but the description provides no additional value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Provision') and resource ('real phone number (SMS + voice)'), clearly distinguishing it from temporary number sibling tools like phone_temp_number. It also states the purpose ('for your agent') and adds cost context.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for a real, paid, likely permanent number ('real phone number' and cost), but does not explicitly mention when to use this tool versus alternatives such as phone_temp_number. There is no when-not-to-use guidance, leaving usage to be inferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource and action, clearly separated by domain prefixes (card_, email_, phone_, tiktok_). The only potential overlap is phone_read_messages vs wait_for_otp, but wait_for_otp is specifically for OTP extraction and is described as a replacement for hand-rolled polling, making the boundary clear. Status pollers are also domain-specific (card_status, tiktok_connect_status, tiktok_operation_status) and not ambiguous.
All tool names follow a consistent snake_case convention with domain-first prefixes (e.g., card_buy, email_send, tiktok_post, phone_temp_number). Even less common names like wait_for_otp and i402_plan are descriptive and stylistically consistent. There are no mixed conventions or vague verbs.
33 tools is above the typical 3-15 range, but the server covers a broad multi-domain purpose (cards, compute, domains, email, phone, TikTok, Twitter, orchestration). Each domain has a focused and coherent set, so the count feels justified rather than bloated. It is slightly high, but not excessively so.
Coverage is solid for email, phone, and TikTok, with full lifecycle operations (create, read, extend, delete/cancel where applicable). However, there are notable gaps: compute has only deploy (no list/stop/delete), domains have only check/register (no list/delete), and Twitter has only post (no read/manage). These gaps could force agents to work around missing resource management.