Skip to main content
Glama
Sign In
Statuser MCP Server

Statuser MCP Server

Official
by statuser-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get the outcome of a test call

notification_phone_test_result
Read-only

Checks the status of a test phone call—calling, answered, no answer, or failed—using the phone ID and call ID returned when the test was placed.

Instructions

Returns the status of a test call placed by notification_phone_test: calling — still going, answered, no_answer or failed.

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

Input Schema

NameRequiredDescriptionDefault
idYesPhone id.
call_idYes`call_id` returned by `notification_phone_test`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral information beyond them: the four-value status state machine returned by the tool, which matters because no output schema exists. It does not disclose latency, whether states are terminal, or error behavior for an invalid call_id.

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?

A single front-loaded sentence naming the return value, then the enumerated outcomes. Every clause carries information; nothing is padded.

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 two-parameter read with no output schema, the description carries the return-value burden well by listing all four statuses. The only real gap is that it does not say the status may still be in progress and require re-polling, which an agent deciding its next step would want.

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

Parameters3/5

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

Schema description coverage is 100%, and the schema already explains that call_id is 'returned by notification_phone_test'. The description restates that linkage rather than adding format, range, or failure semantics, so the baseline 3 applies.

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 ('Returns the status of a test call') and immediately disambiguates from the sibling that initiates the call, notification_phone_test. It also enumerates the four possible outcomes, so an agent knows exactly what comes back without opening anything else.

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 phrase 'placed by notification_phone_test' establishes the call sequence — this tool is the follow-up to a test call — which is the key usage context. It stops short of explicit polling guidance (e.g. that 'calling' is non-terminal and should be re-queried), so there is no when-to-stop instruction.

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

Deploy Server

Other Tools