Call For Me

get_call_status

Poll the status of a call previously placed with place_call. Returns a CallOutcome with one of these statuses (in roughly likely order): queued/placing/ringing/connected — call still in progress, poll again in a few seconds completed — call finished cleanly, structured result available partial — call finished but some questions unanswered voicemail — recipient was voicemail; identified message left no_answer — recipient never picked up busy — recipient line was busy invalid_number — number is not in service rejected_ai — recipient declined to talk to A.I. (do not retry) needs_user_input — recipient needs info only the user can provide online_only — recipient said the task can only be done online timed_out — call exceeded max duration carrier_failure — telephony provider error (safe to retry later) api_error — internal failure (safe to retry)

Always carries a free-form exit_reason string suitable for showing the user.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`call_id`	Yes	The call_id returned by place_call.

TDQS

A4.7/5.0

Behavior4/5

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

With no annotations, the description fully explains the returned CallOutcome and each status. Could explicitly state it's read-only, but the polling nature implies it.

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?

Two-sentence structure with clear purpose first, then a well-organized list of statuses. No fluff.

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?

Comprehensive for a polling tool: explains input, output, status meanings, and retry logic. No missing context.

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?

Only one parameter (call_id), schema already covers its purpose. Description reinforces by linking to place_call and the polling context.

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 it polls call status after place_call, and lists all possible statuses. This distinguishes it from sibling tool place_call.

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?

Explicitly says to poll after placing a call, provides polling intervals for in-progress statuses, and gives retry advice for final statuses (e.g., 'do not retry' for rejected_ai).

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

All Call For Me 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

A4.5/5.0

Disambiguation5/5

The two tools have clearly distinct purposes: place_call initiates a call and returns an ID, while get_call_status polls for the outcome. There is no overlap or ambiguity.

Naming Consistency5/5

Both tools use consistent snake_case with a verb_noun pattern (place_call, get_call_status), making the convention predictable and easy to follow.

Tool Count4/5

With only two tools, the set is minimal but well-scoped for the core workflow of placing a call and checking its status. It is slightly undercounted but reasonable for this narrow domain.

Completeness4/5

The tools cover the essential call lifecycle (place and poll status). A minor gap is the lack of a cancel or list calls feature, but the core task is fully supported.

Resources

Need Help?