Skip to main content
Glama

MeiSIM USA

Buy US numbers (wallet)

buy_numbers

Order new US phone numbers on your MeiSIM account, paid from its prepaid wallet. Prepaid: no returns, no refunds once a number is delivered. Choose billing "daily" (a minimum number of days paid now, then each day from the wallet) or "monthly" (a minimum number of months paid up front). A monthly order also says line_history: "fresh" or "any"; ask the user which. Call get_number_pricing first and tell the user the total. Numbers usually land within about 15 minutes; check with get_order. Safe to retry with the same customer_reference. Needs your API key.

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": {
      "count": "<count>",
      "billing": "<billing>"
    },
    "name": "buy_numbers"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoDaily billing only: days to pay now (at least the minimum).
countYesHow many numbers.
voiceNoAlso calls over SIP (costs more; must be enabled on the account).
monthsNoMonthly billing only: months to pay up front (at least the minimum).
billingYes"daily" or "monthly". See get_number_pricing.
zip_codeNo5-digit US ZIP to pick the number's area, if available.
area_codeNoPreferred 3-digit US area code, if available.
line_historyNoMonthly billing: "fresh" for a number no other account has held (no refund if the carrier blocks it), or "any" for a number from stock that may have been used before. Required for monthly orders.
customer_referenceNoYour own reference for this order; a repeat with the same reference returns the first order.

Output Schema

NameRequiredDescriptionDefault
noteYes
voiceYes
statusYes
billingYes
numbersYes
orderedYes
order_idYes
days_paidYes
deliveredYes
duplicateYes
created_atYes
charged_usdYes
outstandingYes
completed_atYes
refunded_usdYes
customer_referenceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only mark it non-read-only/open-world, so the description carries real weight and delivers: prepaid with no refunds after delivery, minimum up-front days or months, ~15 minute delivery window, and API-key requirement. Nothing here contradicts the annotations.

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 and the no-refund warning immediately after. Dense but nearly every sentence carries a distinct fact; only the parenthetical quoted billing names feel mildly redundant with the schema enums.

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 9-parameter purchase tool with an output schema, it covers the financial risk, required pre-call pricing lookup, delivery timing, follow-up status check, and retry safety. An agent has everything needed to call it correctly and set user expectations.

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 baseline is 3, but the description adds payment semantics the schema does not: that daily billing charges a minimum now then daily, monthly charges a minimum up front, that line_history is required and must be resolved with the user, and that customer_reference is an idempotency key.

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 and resource ('Order new US phone numbers') plus the payment source ('prepaid wallet'), which distinguishes it from sibling lookups like search_us_numbers and get_number_pricing without naming them.

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?

Explicit sequencing: call get_number_pricing first and tell the user the total, ask the user about line_history on monthly orders, check progress with get_order. It also states the retry condition (same customer_reference is safe), which is exactly the alternative-path guidance an agent needs.

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.