CallMCP — Phone Call MCP Server

List Observability Events

list_observability_events

Read-onlyIdempotent

List a business-scoped timeline of compact call-runtime events and redacted integration-delivery attempts. Uses bounded keyset pagination.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_observability_events"
  }
}

Input Schema

Name	Required	Description
`to`	No
`from`	No
`limit`	No
`cursor`	No	Opaque next_cursor returned by the previous page.
`source`	No	Event stream to read (default: all).
`call_id`	No	Runtime-event call UUID filter.
`outcome`	No	Integration-delivery filter.
`provider`	No	Integration-delivery filter.
`severity`	No	Runtime-event filter.
`object_id`	No	Integration-delivery filter.
`operation`	No	Integration-delivery filter.
`event_type`	No	Runtime-event filter.
`business_id`	No	Business ID (optional only when the token can access exactly one business).
`object_type`	No	Integration-delivery filter.
`connection_id`	No	Integration connection UUID filter.
`correlation_id`	No	Runtime-event filter.
`conversation_id`	No	Runtime-event filter.

Output Schema

Name	Required	Description
`error`	No	Present when success is false
`events`	No
`success`	Yes	Whether the tool completed successfully
`pagination`	No
`business_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

B3.2/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 the safety profile is covered. The description adds real value by disclosing that delivery-attempt data is redacted, events are compact summaries, and pagination is bounded keyset - but it says nothing about retention windows or defaults for the time range.

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 tight sentences with no filler, and the resource scope is front-loaded ahead of the pagination detail. Slightly under-specified rather than padded.

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

Completeness3/5

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

With 17 optional parameters, an output schema, and rich annotations, the definition is serviceable but leaves gaps: it never states that from/to bound the timeline, nor how source=all relates to the runtime-only and delivery-only filter sets. An agent could still call it correctly by reading the schema, but the description does not fully cover the tool's complexity.

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 coverage is 82%, so the enum and filter descriptions already carry most parameter meaning. The description reinforces 'business-scoped' (matching the conditionally optional business_id) and keyset pagination (cursor/limit), but adds no semantics for the runtime-vs-delivery filter families that the schema only lightly labels.

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?

Names a specific verb and two concrete resources: a timeline of call-runtime events and integration-delivery attempts. It clearly conveys the scope ('business-scoped') and the two event streams, though it does not distinguish itself from adjacent siblings such as list_tool_execution_logs or list_recent_calls.

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

Usage Guidelines2/5

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

No when-to-use guidance, no exclusions, and no named alternative for the overlapping log/timeline siblings. The agent learns what the tool returns but not the conditions that should route it here rather than to another list tool.

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.