Skip to main content
Glama
Ownership verified

Server Details

AI phone secretary: place calls, read transcripts, list calls, agents, and stats.

Status
Unhealthy
Last Tested
Transport
Streamable HTTP
URL
Repository
KaiCalls/kaicalls-mcp
GitHub Stars
0
Server Listing
KaiCalls MCP Server

Glama MCP Gateway

Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.

MCP client
Glama
MCP server

Full call logging

Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.

Tool access control

Enable or disable individual tools per connector, so you decide what your agents can and cannot do.

Managed credentials

Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.

Usage analytics

See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.

100% free. Your data is private.
Tool DescriptionsA

Average 4.1/5 across 44 of 51 tools scored. Lowest: 3.3/5.

Server CoherenceB
Disambiguation3/5

Tools have distinct purposes overall, but there is overlap (e.g., update_agent_config vs configure_agent_business_rules vs request_kaicalls_update) and several tools handle similar concepts (e.g., get_balance vs list_overage_charges). Descriptions are detailed and help, but the sheer number forces agents to carefully parse intent.

Naming Consistency4/5

Most tools follow a consistent verb_noun pattern (e.g., create_agent, list_agents, send_sms). Minor deviations include longer multi-word names (configure_agent_business_rules) and a single outlier (request_kaicalls_update), but overall the pattern is predictable.

Tool Count2/5

51 tools is excessive for an MCP server. While the domain is broad, this many tools overloads the agent's selection space, making it hard to pick the right one. A more focused split into multiple servers would improve usability.

Completeness3/5

The tool set covers many aspects (numbers, agents, calls, SMS, leads, webhooks, billing, etc.), but notable gaps exist: no get_agent, no delete_agent, no update or delete campaign, and no delete lead. These missing operations may cause agent failures in common workflows.

Discussions

No comments yet. Be the first to start the discussion!

Related MCP Servers

View all MCP Servers

Try in Browser

Your Connectors

Sign in to create a connector for this server.