Skip to main content
Glama

Price of a new number

get_number_pricing
Read-only

Check daily and monthly pricing for a new US number on your MeiSIM account, including activation fees, minimum terms, availability, and voice options, to confirm order eligibility before buying.

Instructions

Show what a new US number costs on your MeiSIM account and whether you can order: the daily rate (minimum days, one-time activation fee, how many are ready right now) and the monthly rate (first month, renewals, minimum months), with and without voice. Call before buy_numbers. Needs your API key.

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": "get_number_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dailyNo
reasonNo
monthlyNo
currencyYes
can_orderYes
voice_noteNo
voice_availableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.5

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare this is a read-only, non-destructive, open-world operation. The description adds useful behavioral context by noting that an API key is required and that the tool reports both pricing and order readiness, though it does not discuss rate limits or other operational constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and then supplies the relevant pricing dimensions in a compact, information-dense form. Every clause contributes useful detail without unnecessary repetition.

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 zero-parameter, read-only pricing tool with an output schema, the description covers what the tool returns, when to call it, and the API key requirement. Nothing essential for correct invocation is missing.

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?

The tool has zero parameters, so there are no parameter semantics to explain. The baseline for a parameterless tool is 4, and the description does not need to compensate for any schema gaps.

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 resource: it shows what a new US number costs on the account, including daily and monthly rates with and without voice. It also distinguishes the tool from buy_numbers by explicitly saying to call it before purchasing.

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?

The description gives clear usage context by saying 'Call before buy_numbers,' which tells the agent when this tool is appropriate. It does not name when-not-to-use cases or alternative pricing/quote tools, so it falls short of the highest level.

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