KaiCalls

Search Available Numbers

search_available_numbers

Read-only

Search the carrier for phone numbers available to purchase (live number inventory). Mirrors GET /api/v1/phone-numbers/search. On the acquisition surface, call set_owner_phone first (or record a decline) — don't search or buy a number for a signup with no way to be reached.

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

A4/5.0

Behavior4/5

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

Annotations already cover read-only, non-destructive, open-world and non-idempotent behavior. The description adds beyond that by clarifying this hits live carrier inventory ('live number inventory'), mapping to the upstream endpoint, and prescribing the acquisition workflow prerequisite. It does not discuss result freshness/volatility beyond the inventory note.

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?

Two sentences, purpose front-loaded, then the workflow caveat. No filler; every clause carries information (endpoint mirror, inventory liveness, prerequisite).

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 an output schema present, return values need no explanation, and the schema plus annotations cover safety and inputs. The description covers purpose and the acquisition prerequisite, but does not point to the natural next step (buy_number) or note that results are transient, leaving a minor gap.

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%, so every parameter (limit, country, area_code, business_id) is already documented. The description adds no syntax, defaults, or format detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (search) and resource (carrier phone numbers), and scopes it with 'available to purchase (live number inventory)', which semantically separates it from list_numbers (owned numbers) and buy_number. It does not name a sibling explicitly, so it falls short of the top score.

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?

Gives a concrete prerequisite for the acquisition surface ('call set_owner_phone first (or record a decline)') plus an explicit exclusion ('don't search or buy a number for a signup with no way to be reached'). It stops short of a 5 because it never names the alternative tool to use for other conditions.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.