Skip to main content
Glama

Call volume and duration totals

call_summary
Read-onlyIdempotent

Totals over a date range: calls placed and received, answered vs missed, and total/average duration, with a daily series. Defaults to the last 7 days. Counts the switch's records when the organisation has a telephony data source, and cpass's own call records when it does not; source says which. 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_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateToNoISO date or date-time. Default now
dateFromNoISO date or date-time. Default 7 days ago

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 read-only, idempotent, closed-world behavior, so the closing 'Read only' adds little. The description adds meaningful context beyond annotations: it explains that counts come from the switch's telephony records when available, otherwise from cpass's own call records, and that `source` identifies which was used.

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?

Front-loads the metric scope and daily series, then the default window and source caveat. It is efficient and well ordered, with only minor redundancy in the final 'Read only' sentence.

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 aggregation tool with no output schema, the description supplies the key metric list, daily series, default window, and data-source caveat. Possible timezone or date-boundary details are absent, but the core behavior is complete enough to call 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 coverage is 100%, so both optional date parameters are already fully documented. The description restates the 7-day default window but adds no date syntax, timezone, or boundary-inclusivity details beyond the 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?

States a specific aggregation over a date range: calls placed/received, answered/missed, total/average duration, and a daily series. The word 'Totals' and the daily series clearly distinguish it from list-oriented siblings such as call_list, though no sibling is explicitly named.

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?

Implies use for aggregate call-volume and duration reporting over a date range and notes the default last 7 days. It does not explicitly say when to choose this over call_list, call_outcome, or metrics_summary, nor does it state exclusions or prerequisites.

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.