CallMCP — Phone Call MCP Server

Read CallRail setup

get_callrail

Read-onlyIdempotent

Read a business's CallRail call-tracking setup. action=status returns the connected CallRail account, which CallRail companies feed which business, every company the saved key can see (with its company_id), and the businesses you can link them to. action=list_trackers (with link_id from status) returns that company's tracking numbers, where each one rings now, and whether it already rings a KaiCalls line. If nothing is connected yet, ask the person for their CallRail API key and use manage_callrail connect.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "business_id": "<business_id>"
    },
    "name": "get_callrail"
  }
}

Input Schema

Name	Required	Description	Default
`action`	No
`link_id`	No
`business_id`	Yes

Output Schema

Name	Required	Description	Default
`error`	No
`success`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered; the description adds real behavioral context on top, including the state dependency between the two actions and the onboarding fallback. It stops short of covering failure modes (invalid link_id, revoked key), which is the only notable gap.

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?

Front-loaded with the purpose, then the two actions in the order they must be called, then the fallback. Dense but every sentence carries information; the middle sentence is long enough to slow scanning slightly.

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

Completeness5/5

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

For a two-mode read tool with a rich output schema, the definition supplies the mode semantics, the parameter dependency, and the escalation path. Return values are already covered by the output schema, so nothing an agent needs to invoke this correctly is missing.

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

Parameters4/5

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

Schema description coverage is 0%, so the description carries the load, and it does explain the two action values and where link_id comes from. business_id is only implicitly covered by "a business's ... setup" and "which businesses you can link them to", leaving its exact role slightly loose.

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?

States a specific verb and resource ("Read a business's CallRail call-tracking setup") and then decomposes the two modes, action=status for account/company linkage and action=list_trackers for tracking numbers. This clearly separates it from the write-side sibling manage_callrail without needing to open either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit sequencing (list_trackers takes link_id from status) and an explicit alternative for the not-connected case: ask for the API key and use manage_callrail connect. Both the when-to-use and the when-to-use-something-else paths are stated.

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

All CallMCP — Phone Call MCP Server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.