Wavix

api_keys_create

Creates an API key. Optional IP restrictions can be configured to limit access.

Input Schema

TableJSON Schema

Name	Required	Description
`calls`	No	Access call records and active calls, and control live call actions such as starting, answering, ending, audio playback, DTMF, streaming, and transcription requests.
`label`	No	API key label.
`trunks`	No	View, create, update, and delete SIP trunks and their settings.
`two_fa`	No	View 2FA service details and verification logs, trigger OTPs by voice or SMS, and validate verification codes.
`account`	No	View and update account profile information and timezone.
`billing`	No	Access invoices, balance, payment methods, usage reports, and billing settings, including payment method updates.
`numbers`	No	View, buy, release, and configure phone numbers, browse inventory, and manage the cart.
`messages`	No	Access message history and Sender IDs, send messages, manage opt-outs, and create or delete Sender IDs.
`webhooks`	No	List, create, and delete webhooks.
`campaigns`	No	View campaign analytics and Sender ID or Brand status, schedule bulk voice or SMS campaigns, register Brands, and create short links.
`is_active`	No	Indicates whether the API key should be activated upon creation.
`validator`	No	View number validation results and trigger single or bulk validation or HLR lookup requests.
`embeddable`	No	Manage widget tokens, including listing, viewing, creating, updating, and deleting them.
`recordings`	No	List, download, and delete call recordings.
`subaccounts`	No	Manage subaccounts: list and view them, create, update, and suspend them.
`permitted_ips`	No	List of permitted IP addresses for this API key. Each must be a valid IPv4 address. Required when `is_restriction` is true.
`is_restriction`	No	Indicates whether to restrict API key access by IP address. When enabled, only requests from IP addresses listed in `permitted_ips` are allowed.
`is_scopes_enabled`	No	When `true`, scope fields below are enforced. When `false` (default), the key has full access. Omitted scope fields default to `{ allow: none }`, so with `is_scopes_enabled: true` and no scopes set the key has no access.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	API key ID.
`calls`	Yes	Access call records and active calls, and control live call actions such as starting, answering, ending, audio playback, DTMF, streaming, and transcription requests.
`label`	Yes	API key label.
`value`	Yes	API key value.
`trunks`	Yes	View, create, update, and delete SIP trunks and their settings.
`two_fa`	Yes	View 2FA service details and verification logs, trigger OTPs by voice or SMS, and validate verification codes.
`account`	Yes	View and update account profile information and timezone.
`billing`	Yes	Access invoices, balance, payment methods, usage reports, and billing settings, including payment method updates.
`numbers`	Yes	View, buy, release, and configure phone numbers, browse inventory, and manage the cart.
`messages`	Yes	Access message history and Sender IDs, send messages, manage opt-outs, and create or delete Sender IDs.
`webhooks`	Yes	List, create, and delete webhooks.
`campaigns`	Yes	View campaign analytics and Sender ID or Brand status, schedule bulk voice or SMS campaigns, register Brands, and create short links.
`is_active`	Yes	Indicates whether the API key is active.
`validator`	Yes	View number validation results and trigger single or bulk validation or HLR lookup requests.
`created_at`	Yes	Creation date and time in ISO 8601 format.
`embeddable`	Yes	Manage widget tokens, including listing, viewing, creating, updating, and deleting them.
`recordings`	Yes	List, download, and delete call recordings.
`subaccounts`	Yes	Manage subaccounts: list and view them, create, update, and suspend them.
`last_used_at`	Yes	Timestamp of the most recent authenticated request made with this key.
`permitted_ips`	Yes	List of permitted IP addresses. If `is_restriction` is false, an empty list means no IP restrictions. If `is_restriction` is true, an empty list prevents all requests.
`is_restriction`	Yes	Indicates whether IP restrictions are enabled. When enabled, the API key works only from IP addresses in `permitted_ips`.
`is_scopes_enabled`	Yes	When `true`, the key is restricted to the permissions defined in the scope fields below. When `false`, the key has full access.

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states creation and IP restriction capability. It does not mention that the key/secret is typically shown only once, that this is a long-lived write operation, or any authentication/permission requirements.

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 two sentences and front-loaded with the primary action. The second sentence about IP restrictions is relevant and earns its place without redundancy.

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

Completeness3/5

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

An output schema exists and the input schema is fully self-documenting, which lowers the burden on the description. However, the description lacks usage alternatives and critical behavioral notes (e.g., full access when scopes are disabled), leaving it adequate but not fully complete given the tool's complexity.

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%, so the baseline is 3. The description adds a minimal paraphrase of permitted_ips and is_restriction ('IP restrictions'), but does not meaningfully extend beyond the schema's already detailed parameter descriptions.

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 clearly states the tool 'Creates an API key' with a specific verb and resource, distinguishing it from siblings like api_keys_delete or api_keys_list. The additional mention of optional IP restrictions adds scope without confusion.

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 is provided on when to use this tool versus alternatives, nor any mention of prerequisites or post-creation steps. The agent must infer usage solely from the tool name and brief description.

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.

api_keys_create

Input Schema

Output Schema

TDQS

Glama MCP Gateway

TDQS

Resources