Skip to main content
Glama

List calls

call_list
Read-onlyIdempotent

This organisation's call log, newest first. Filter by date range, call type, status, the dialled number, or the caller ID used. Each call's call_id is its unique id; row_id, when present, is cpass's internal row number. 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": "call_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo0-based page number, default 0
callIdNoA specific call's unique id (call_id) or sid
dateToNoISO date or date-time
statusNo
perPageNoPage size, default 100
callTypeNo
callerIdNo
dateFromNoISO date or date-time
dialedNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 safety profile is covered. The description adds real value beyond them: result ordering ('newest first') and the distinction between call_id (unique id) and row_id (internal row number), which an agent could not infer from the schema.

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?

Three short sentences, front-loaded with the resource and ordering, then filters, then id semantics. 'Read only' duplicates the readOnlyHint annotation and is the only mildly redundant element.

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?

For a 9-parameter tool with no output schema and no enums, the description covers filtering and identity well but leaves the allowed values for status and callType unexplained, and says nothing about pagination behavior beyond what the schema states.

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 only 56%, so the description must compensate, and it does: it maps the filterable parameters (date range, call type, status, dialled number, caller ID) and clarifies the callId/row_id identity semantics. It does not enumerate valid values for status or callType, which remain undocumented.

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?

States a specific resource and scope: 'This organisation's call log, newest first', plus the filterable dimensions. It is clearly a list/read tool, though it does not name a sibling (e.g. calls_live) to differentiate itself from the live-call tool.

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?

Usage is implied by the filter list — use it to retrieve historical calls narrowed by date, type, status, number or caller ID. There is no explicit when-to-use/when-not guidance and no pointer to alternatives such as calls_live or call_transcript for related needs.

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.