Skip to main content
Glama
team-telnyx

Telnyx MCP Server

Official
by team-telnyx
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

create_call_control_application

Set up a call control application on Telnyx to manage inbound and outbound voice calls with configurable webhooks, DTMF settings, and connection parameters.

Instructions

Create a call control application.

 Args:
    application_name: Required. A user-assigned name to help manage the application.
    webhook_event_url: Required. The URL where webhooks related to this connection will be sent. Must include a scheme, such as 'https'.
    active: Optional boolean. Specifies whether the connection can be used. Defaults to True.
    anchorsite_override: Optional. Directs Telnyx to route media through the site with the lowest round-trip time. Defaults to "Latency".
    dtmf_type: Optional. Sets the type of DTMF digits sent from Telnyx to this Connection. Defaults to "RFC 2833".
    first_command_timeout: Optional boolean. Specifies whether calls should hangup after timing out.
    first_command_timeout_secs: Optional integer. Seconds to wait before timing out a dial command. Defaults to 30.
    inbound: Optional dictionary. Inbound call settings with these possible keys:
        - channel_limit: Optional integer. Maximum number of concurrent inbound calls.
        - shaken_stir_enabled: Optional boolean. Enable SHAKEN/STIR verification for inbound calls.
        - sip_subdomain: Optional string. SIP subdomain for the application.
        - sip_subdomain_receive_settings: Optional string. Settings for SIP subdomain receiving.
    outbound: Optional dictionary. Outbound call settings with these possible keys:
        - channel_limit: Optional integer. Maximum number of concurrent outbound calls.
        - outbound_voice_profile_id: Optional string. ID of the outbound voice profile to use.
    webhook_api_version: Optional. Determines which webhook format will be used. Defaults to "1".
    webhook_event_failover_url: Optional. The failover URL for webhooks if the primary URL fails.
    webhook_timeout_secs: Optional integer. Seconds to wait before timing out a webhook.
Returns:
 Dict[str, Any]: Response data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYes

Tool Definition Quality

B3.4/5.0
Behavior3/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It implies a write operation ('Create') and documents many configuration parameters with defaults, which adds useful context. However, it lacks critical behavioral details like authentication requirements, rate limits, error handling, or whether the creation is idempotent/reversible, leaving significant gaps for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately front-loaded with the core purpose, but the parameter documentation is verbose and could be more structured. While comprehensive, some details like nested dictionary keys could be streamlined. The 'Returns' section is minimal but adequate given no output schema exists.

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?

For a complex creation tool with 14+ parameters, nested objects, and no annotations/output schema, the description provides good parameter coverage but lacks important contextual elements. Missing are authentication requirements, error responses, typical use cases, and relationship to sibling tools. The parameter documentation is strong, but other aspects remain underspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description provides extensive parameter documentation that fully compensates for the 0% schema description coverage. It clearly explains all 14+ parameters (including nested structures for inbound/outbound), their purposes, data types, defaults, and constraints (e.g., URL scheme requirement). This adds substantial value beyond the minimal input schema that only shows a generic 'request' object.

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 the verb 'Create' and the resource 'call control application', providing specific purpose. However, it doesn't differentiate from sibling tools like 'create_assistant' or 'create_messaging_profile' beyond the resource name, missing explicit comparison to similar creation tools in the same domain.

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?

The description provides no guidance on when to use this tool versus alternatives. There are no prerequisites mentioned (e.g., required permissions, account setup), no comparison to sibling tools like 'get_call_control_application' or 'list_call_control_applications', and no context about typical workflows where this creation is appropriate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/team-telnyx/telnyx-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server