Skip to main content
Glama
avarole-mcp
by Sbaig3229

avarole_call_stats

Read-only

Retrieve call totals for the last N days to track minutes, average length, sentiment, and plan minutes used and remaining.

Instructions

Totals for the last N days: calls, minutes, average length, sentiment, and the plan's minutes used and left.

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

Input Schema

NameRequiredDescriptionDefault
daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description adds the lookback-window framing and the shape of the results. It stops short of disclosing scope (workspace-wide vs per-agent), how sentiment is aggregated, or whether plan minutes reflect the billing period.

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?

A single sentence with no filler, front-loaded with the aggregation scope before the metric list. Nothing in it is redundant, though the colon-delimited metric list could be tightened slightly.

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?

With no output schema, the description does the necessary work of enumerating what the aggregate contains, which is the key thing an agent needs to decide to call it. The remaining gap is data scope (whose calls are totaled), which matters for interpreting plan minutes used/left.

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?

The single parameter has 0% schema description coverage, so the description carries the burden; it clarifies that 'days' is a trailing lookback window ('last N days'), which is more than the bare title 'Days' conveys. It does not state that the default is 30, whether the current day is included, or whether the range is bounded.

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 gives a specific verb-scope and resource ('Totals for the last N days') and enumerates the exact metrics returned: calls, minutes, average length, sentiment, and plan minutes used/left. The call/sentiment metrics make it distinguishable in practice from avarole_ticket_stats, though it never names or contrasts a sibling explicitly.

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 word 'Totals' signals an aggregation/summary role rather than a listing role, which implicitly steers an agent away from avarole_list_calls toward this tool for reporting. There is, however, no explicit statement of when to use this versus the ticket stats or list tools, and no prerequisites or exclusions are given.

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