KaiCalls

Search Available Numbers

search_available_numbers

Read-only

Search the carrier for phone numbers available to purchase (real-time Twilio inventory lookup). Mirrors GET /api/v1/phone-numbers/search.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max results to return (default 10, max 20).
`country`	No	Two-letter country code (default US).
`area_code`	No	Preferred area code (optional).
`business_id`	No	Search that business's carrier inventory (optional; defaults to the platform carrier).

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present when success is false
`success`	Yes	Whether the tool completed successfully
`available_numbers`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 10, 2026

addedInput schema / properties / business_id

Added value: +{
+  "description": "Search that business's carrier inventory (optional; defaults to the platform carrier).",
+  "type": "string"
+}

AddedJul 9, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already communicate read-only and non-destructive behavior. The description adds the meaningful 'real-time Twilio inventory lookup' detail, but does not disclose pagination, rate limits, or that results may change between calls.

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 concise and front-loaded with the core action ('Search the carrier for phone numbers available to purchase'), with the API mirror note as useful supporting context. No filler or redundant restatement of the tool name.

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

Completeness4/5

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

With a rich input schema, output schema, and safety annotations, the description covers the essential purpose and real-time nature of the operation. It does not explicitly guide the agent to use this before buy_number, but the context is mostly complete for a simple read-only lookup.

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?

The schema description coverage is 100%, so all parameters are already documented in the input schema. The description adds no extra semantic nuance about parameter usage beyond framing this as an inventory lookup.

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 names a specific operation: 'Search the carrier for phone numbers available to purchase,' and clarifies it as a real-time Twilio inventory lookup. This clearly differentiates it from purchasing and number-management siblings like buy_number, attach_number, or list_* tools.

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

Usage Guidelines3/5

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

The phrase 'available to purchase' implies this tool should be used to discover numbers before buying or attaching them, but the description never explicitly says when to use it versus buy_number or attach_number. Guidance is implied rather than stated.

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

All KaiCalls tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.