Skip to main content
Glama
okareo-ai

Okareo MCP Server

Official
by okareo-ai

Connect Voice Integration

connect_voice_integration

Connect a voice provider to route its traffic into Okareo monitoring. Returns an integration ID to generate the webhook URL for your provider console.

Instructions

Connect a voice provider so its traffic flows into Okareo monitoring.

    Creates a provider integration. The returned integration carries an id
    and a public_id — pass the provider + public_id to get_voice_webhook_url
    to obtain the inbound webhook endpoint to paste into the provider's
    console.

    Args:
        provider: Voice platform — one of: retell, twilio, vapi, elevenlabs.
        webhook_auth_type: Webhook authentication type expected by Okareo
            for this provider (provider-specific — see Okareo docs).
        secrets: Provider-specific secret values (opaque pass-through; the
            response never echoes raw secrets, only a summary).
        metadata: Optional free-form metadata object.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
secretsYes
metadataNo
providerYes
webhook_auth_typeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Beyond the annotations, the description adds meaningful behavioral details: the response carries an id and public_id, secrets are never echoed and only summarized, and webhook_auth_type is provider-specific. This helps the agent understand side effects and security aspects. No contradiction with annotations.

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 about 150 words and well-structured, with a clear purpose statement followed by parameter explanations. Every sentence adds value; no fluff or repetition. It's slightly longer than necessary but appropriate given the parameter complexity.

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?

The description covers the main success behavior (creation, returned id/public_id) and directs to the next step (get_voice_webhook_url). With an output schema present, it doesn't need to enumerate all return fields. It also covers all parameters and provider options, making it sufficiently complete for this mutating tool.

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 schema has 0% description coverage, so the Args section in the description carries the full burden. It adds substantial meaning: lists allowed provider values (retell, twilio, vapi, elevenlabs), explains webhook_auth_type is provider-specific, describes secrets as opaque pass-through, and notes metadata is optional. This fully compensates for the missing schema 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's action: "Connect a voice provider so its traffic flows into Okareo monitoring" and "Creates a provider integration." This is a specific verb+resource, and it distinguishes from sibling tools like update_voice_integration or rotate_voice_integration_secret by focusing on initial setup.

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?

The description provides clear context for when to use it (connecting a voice provider) and even mentions the follow-up step of using get_voice_webhook_url with the returned public_id. It doesn't explicitly state exclusions or alternatives, but the focus on creation makes the usage fairly obvious.

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/okareo-ai/okareo-mcp'

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