seven-mcp

Official

Overview Schema Source Related Servers Discussions Admin

get_available_numbers

Retrieve a list of phone numbers available for purchase, filtered by country, type, and features like SMS or voice support.

Instructions

List available phone numbers for purchase

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_available_numbers"
  }
}

Input Schema

Name	Required	Description
`country`	No	Country code to filter available numbers
`type`	No	Number type (e.g., mobile, landline)
`features_sms`	No	Filter numbers supporting SMS
`features_a2p_sms`	No	Filter numbers supporting A2P SMS
`features_voice`	No	Filter numbers supporting voice calls

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1May 29, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. It only states 'list', implying a read operation, but does not discuss side effects, authentication needs, rate limits, or any behavioral nuances. It adds minimal value beyond the tool name.

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?

A single short sentence that is to the point and not wasteful. However, it could be slightly more structured or include additional context without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 5 optional parameters, no output schema, and many sibling tools, the description is too minimal. It fails to mention pagination, response format, or any filtering behavior, leaving the agent underinformed.

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 description coverage is 100% with each parameter explained (country, type, features). The description adds no extra meaning beyond the schema, meeting the baseline for high coverage.

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 'List available phone numbers for purchase' clearly states the action (list) and resource (available phone numbers for purchase). It distinguishes from siblings like get_active_numbers (lists already purchased numbers) and get_number (single number detail).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives such as get_active_numbers or order_number. It does not specify that this is for numbers available to buy, nor does it mention when not to use it.

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