Skip to main content
Glama

Calls in progress right now

calls_live
Read-onlyIdempotent

Every call currently active in this organisation — ringing, connected or on hold. Note: cpass restricts this endpoint to admin-tier roles, so it may 403 for a user whose portal role is an ordinary agent rather than an admin, independent of what this connection was granted. Read only.

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": "calls_live"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the trailing "Read only." adds nothing. The genuinely valuable addition is the authorisation disclosure: the endpoint may return 403 based on portal role independently of connection grants, which is behavior no annotation captures.

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?

The scope statement is front-loaded in the first sentence, with the role caveat second. No filler, no repetition of the title, and every clause carries information the agent needs before calling.

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 no-param, read-only snapshot tool with full annotation coverage, the definition covers scope, states and the main failure mode. The one gap is that, with no output schema, it never hints at what a live call record contains.

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?

The tool takes zero parameters, so there is no parameter meaning to add and the baseline applies. Nothing in the description conflicts with the empty schema.

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?

"Every call currently active in this organisation — ringing, connected or on hold" gives a specific resource plus scope and the exact states covered, which cleanly separates it from historical call siblings like call_list. It never names an alternative sibling explicitly, so differentiation is conveyed only through the temporal qualifier.

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

Usage Guidelines3/5

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

The description implies the use case (snapshot of live traffic) and adds a real precondition — admin-tier role required, may 403 for ordinary agents. It gives no explicit when-to-use versus call_status/call_list, and no exclusion conditions beyond the role caveat.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.