Skip to main content
Glama

List recent calls

list_calls
Read-only

Recent calls, newest first: id, call SID, when, number, crew member, whether it was handed to your person, outcome, summary, and whether a transcript and recording exist. Reps see their own calls; managers and admins see all.

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_calls"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOptional phone number; only calls to or from it.
limitNoHow many, 1–50. Default 10.
sinceNoOptional ISO time; only calls after it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint=false, so safety is covered; the description adds ordering (newest first), a concrete field manifest, and a role-based visibility rule that materially affects how results should be interpreted. It stops short of mentioning pagination limits beyond the schema's limit cap or default behavior when results are truncated.

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: the first front-loads the resource and ordering then lists fields; the second covers access scope. The field enumeration is dense but each item tells the agent what it can rely on, so little is wasted.

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

Completeness5/5

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

With no output schema, the description carries the return-value burden and does so by naming every field, including derived booleans for transcript and recording availability. Combined with fully documented parameters and annotations covering read-only safety, an agent has enough to call this correctly.

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%, so the schema already fully documents 'to', 'limit', and 'since'. The description adds no parameter-level meaning (e.g. whether 'to' matches either direction is only in the schema), so baseline 3 applies.

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 makes clear this returns a list of recent calls with newest first, and enumerates the returned fields, so an agent knows exactly what resource it gets. It does not name a verb ('list') explicitly nor differentiate itself from get_call_transcript, which is the natural follow-up when a transcript exists.

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?

There is no when-to-use guidance, no exclusions, and no named alternative — an agent gets no signal about when to call this versus get_call_transcript or other call-related siblings. The permission note ('Reps see their own calls; managers and admins see all') explains result scope but is not usage guidance.

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.