Wavix

my_numbers_update

Updates a phone number.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Phone number ID.
`sms_relay_url`	No	Callback URL for inbound messages. Set to `null` to remove routing.
`call_status_url`	No	Callback URL for call status updates.
`transcription_enabled`	No	Indicates whether transcription is enabled.
`call_recording_enabled`	No	Indicates whether call recording is enabled.
`transcription_threshold`	No	Transcription threshold in seconds.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Phone number ID.
`city`	Yes	City or rate center where the phone number originates.
`cnam`	Yes	Indicates whether CNAM is enabled.
`added`	Yes	Date and time the phone number was purchased in ISO 8601 format.
`label`	Yes	Label assigned to the phone number.
`state`	No	State where the phone number originates. For non-US numbers, this field may be null.
`number`	Yes	Phone number.
`status`	Yes	Phone number status. `active` means the number can receive and place calls; `inactive` means it cannot.
`country`	Yes	Country where the phone number originates.
`per_min`	Yes	Price per inbound minute in USD.
`seconds`	Yes	Total inbound call duration in seconds for current month.
`channels`	Yes	Maximum number of concurrent inbound calls.
`free_min`	No	Number of free inbound minutes.
`documents`	Yes	Uploaded documents for the phone number.
`unlimited`	No	Indicates whether usage is unlimited.
`paid_until`	Yes	Date until which the number is paid.
`destination`	Yes	Inbound call destinations set for the phone number.
`monthly_fee`	Yes	Monthly fee in USD.
`sms_enabled`	Yes	Indicates whether SMS is enabled.
`domestic_cli`	Yes	Indicates whether the number can be used as the Caller ID for local calls.
`require_docs`	Yes	Documents required to activate the phone number.
`sms_relay_url`	Yes	Callback URL for inbound SMS and MMS messages.
`activation_fee`	Yes	One-time activation fee in USD.
`call_status_url`	No	Callback URL for call status updates.
`country_short_name`	Yes	Two-letter ISO country code.
`transcription_enabled`	Yes	Indicates whether transcription is enabled.
`call_recording_enabled`	Yes	Indicates whether call recording is enabled.
`transcription_threshold`	Yes	Minimum call duration in seconds to trigger transcription.

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only mentions 'Updates a phone number' without explaining partial vs. full update semantics, idempotency, or effects on existing settings. The schema describes parameter details, but the description itself adds no behavioral context.

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?

The description is extremely concise at four words, single sentence, and front-loaded. It wastes no words, but its brevity borders on under-specification, which is captured in other dimensions.

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?

Despite rich schema and an output schema, the description is too minimal for a mutation tool. It lacks any information about when to use it, how it differs from other numeric update tools, or behavioral nuances that would help an agent invoke it correctly. Even with the schema, this is insufficient.

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 coverage is 100% with detailed descriptions and examples for all six parameters. The tool description adds no parameter-level meaning beyond the schema, so the baseline score of 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?

The description clearly states 'Updates a phone number,' providing a specific verb and resource. However, it does not distinguish itself from sibling tools like my_numbers_sms_update or my_numbers_destinations_update, which also modify phone number settings.

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?

There is no guidance on when to use this tool versus the more targeted my_numbers_sms_update or my_numbers_destinations_update. The description offers no context about which fields are appropriate or exclusions, so an agent cannot know when to choose this tool.

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

All Wavix 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.

TDQS

B3/5.0

Disambiguation4/5

Tools are organized by resource with a clear action suffix (create/list/get/update/delete), making most purposes distinct. However, with 122 tools, some pairs like `cdrs_list` vs `cdrs_list_all` or `ten_dlc_brand_campaigns_list` vs `ten_dlc_campaigns_list` could cause confusion without careful reading of descriptions.

Naming Consistency5/5

All tool names follow a consistent `resource_action` snake_case pattern (e.g., `api_keys_create`, `call_control_answer`, `ten_dlc_brands_list`). Verbs are standardized across the set, with only a few exceptions like `check` or `nudge` that still fit the verb-first style. No mixed casing or inconsistent separators.

Tool Count1/5

At 122 tools, this is an extremely large surface that overwhelms the typical MCP agent's ability to select the right tool. Even though the count reflects the full Wavix API, the sheer number far exceeds the 50+ threshold for 'extreme mismatch' and is impractical for most use cases.

Completeness4/5

The tool set covers a broad range of communications features: numbers, calls, messages, billing, CDRs, sub-accounts, 10DLC compliance, speech analytics, and WebRTC. Missing operations like `sub_accounts_delete` or a 2FA service management endpoint are minor gaps that can be worked around via portal or other tools, but overall lifecycle coverage is strong.

my_numbers_update

Input Schema

Output Schema

TDQS

Glama MCP Gateway

TDQS

Resources