Skip to main content
Glama

Get call report

get_call_report
Read-onlyIdempotent

Call totals for this account over the last N days: incoming, answered, unanswered and voicemail counts, answer rate, talk time, and the outgoing calls broken down by month and destination with their minutes. unreachable_count is the part of unanswered where no phone could ring because the business's extensions were offline (not registered): a technical fault in phones or network, not customers hanging up. ai_answered_count is the part of answered that an AI phone agent took. A cold range can come back partial: meta.warming true means the numbers are still being gathered and are not final.

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

Input Schema

NameRequiredDescriptionDefault
daysNoHow many calendar days to measure, today included (7 = today and the 6 before; this month = today's day of the month). Defaults to 30.
fieldsNoOptional: return only these fields of each record.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description does add real behavioral context beyond that: the semantics of unreachable_count versus unanswered, what ai_answered_count includes, and the meta.warming caveat that a cold range returns non-final numbers. It still says nothing about timezone boundaries, how monthly buckets are cut, or cost/latency, so the extra context is useful but partial.

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?

It is front-loaded with the core purpose and then layers disambiguations for the non-obvious counters, with no filler or marketing language. The single dense paragraph runs long and would read better split into purpose, field semantics, and the partial-data caveat, but every sentence carries information.

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?

There is no output schema, so the description correctly carries the burden of explaining the returned metrics, and it covers the ambiguous ones (unreachable_count, ai_answered_count, meta.warming). For a two-optional-parameter read-only report this is nearly sufficient; only scope questions like account versus team/agent coverage and the days-window timezone remain unaddressed.

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% and both parameters (days, fields) are fully documented in the schema, including the inclusive counting rule and the enum of selectable fields, so the baseline is 3. The description adds nothing beyond a passing mention of 'last N days' and does not mention the fields projection at all.

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 names the resource (call totals for this account) and the exact scope (last N days), then enumerates what is measured: incoming, answered, unanswered, voicemail, answer rate, talk time, and outgoing calls by month and destination. It is clear what the tool returns, but it never contrasts itself with siblings such as get_agent_report, get_conversation_report or get_call_center_status, so an agent must infer which report to pick.

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 explicit when-to-use guidance, no prerequisites, and no exclusions or alternative named among the many sibling report tools. Usage is only implied by the account-wide scope and the days window, so an agent has no stated rule for choosing this over the agent-, team-, or conversation-level reports.

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.

Resources