Skip to main content
Glama
avarole-mcp
by Sbaig3229

avarole_list_calls

Read-only

Retrieve recent support calls and conversations, newest first, with timing, agent, sentiment, rating, and summary; filter by agent and paginate results.

Instructions

Recent calls and conversations, newest first: when, how long, which agent, sentiment, rating and a summary.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
agent_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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. The description adds genuinely useful behavior beyond that: result ordering (newest first) and the fields carried in each record (duration, agent, sentiment, rating, summary). It omits pagination behavior, whether a total count is returned, and whether results are scoped to the caller's workspace.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with no filler, front-loaded with the resource and ordering before the field enumeration. Every clause earns its place by telling the agent what comes back.

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?

With no output schema, the field enumeration is valuable and largely covers what the agent should expect to receive. But for a three-parameter listing tool with 0% schema coverage and no annotation detail on paging, the absence of any limit/offset/agent_id explanation leaves a real gap for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% — limit, offset, and agent_id are bare titles with defaults and no explanatory text. The description does not mention any of the three parameters, so nothing compensates: the agent gets no statement of the default page size, what offset counts, or that agent_id filters the listing to one agent.

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 the resource ('calls and conversations'), the ordering ('newest first'), and the fields returned, which is enough to separate it from siblings such as avarole_list_tickets or avarole_list_agents. However, the verb is only implied by the tool name; the description itself is a noun phrase rather than an explicit 'list calls' statement, and it never explicitly contrasts itself with avarole_call_stats.

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 at all — no indication of when to prefer this over avarole_call_stats, avarole_get_ticket, or avarole_get_agent, and no exclusions. The only implicit steer is 'recent', which hints at browsing rather than analytics, but the agent must infer that.

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