Skip to main content
Glama
Sign In

KaiCalls

by com.kaicalls
OverviewDiscussionsAdmin

Check Call Status

check_call_status
Read-onlyIdempotent

Check the status of a call by its ID: any question Kai is waiting on (pending_question), a voicemail message left, or the business calling back. Also takes the intent_id of a call scheduled for calling hours and says when it goes out

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": {
      "call_id": "<call_id>"
    },
    "name": "check_call_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
call_idYesThe call ID to check, or the intent_id make_call returned for a scheduled call

Output Schema

NameRequiredDescriptionDefault
callNo
errorNoPresent when success is false
successYesWhether the tool completed successfully
pending_questionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / call_id / description
      Previous value: -"The call ID to check"New value: +"The call ID to check, or the intent_id make_call returned for a scheduled call"
  2. Changed1 schema field changed
    • addedOutput schema / properties / pending_question
      Added value: +{
+  "properties": {
+    "answer_within_seconds": {
+      "type": "integer"
+    },
+    "asked_at": {
+      "type": "string"
+    },
+    "open_questions": {
+      "type": "integer"
+    },
+    "question": {
+      "type": "string"
+    },
+    "question_id": {
+      "type": "string"
+    },
+    "seconds_waiting": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    }
+  },
+  "type": [
+    "object",
+    "null"
+  ]
+}
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is fully covered and the description's contribution is the meaning of the possible statuses (waiting on a question, voicemail, callback). It does not discuss failure behavior for an unknown or expired ID, and since an output schema exists it needn't describe the return payload.

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?

Two sentences, front-loaded with the primary action and the possible statuses, with the scheduled-call case as a natural second thought. The second sentence is slightly loose ("Also takes...") but nothing is wasted.

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?

For a single-parameter read tool with full annotation coverage and an output schema, the description covers what the agent needs: the input forms and what the answer means. Only edge-case behavior (invalid/unknown ID, timing of scheduled-call queries) is left unstated.

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 coverage is 100% and the parameter is already documented as accepting either a call ID or an intent_id. The description still adds value by explaining the semantic consequence of the second form — the result tells you when the scheduled call goes out — which the schema alone does not convey.

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 states a specific verb and resource ("Check the status of a call by its ID") and enumerates the concrete outcomes it can report: pending_question, voicemail left, or business calling back. That enumeration implicitly separates it from content-fetching siblings like get_transcript or get_call_recording, though it never names an alternative outright.

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?

It gives clear usage context: call this with a call ID to see where a call stands, or with the intent_id returned by make_call to learn when a scheduled call goes out. That covers both realistic entry paths, but there is no explicit when-not guidance or named alternative for broader lookup cases such as list_recent_calls.

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

All KaiCalls toolsInspect
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.

Resources