Skip to main content
Glama
avarole-mcp
by Sbaig3229

avarole_ticket_stats

Read-only

Retrieve ticket totals for the last N days, covering opened, resolved, open, urgent, average resolution time, and breakdowns by priority and topic.

Instructions

Ticket totals for the last N days: opened, resolved, open now, urgent, average resolution time, by priority and topic.

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

Input Schema

NameRequiredDescriptionDefault
daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, non-open-world operation, so the safety profile is clear. The description adds useful information about which metrics are returned, but it does not disclose computation details such as whether 'last N days' includes today, timezone handling, or how averages are calculated.

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?

The definition is a single, front-loaded sentence with no filler. The colon-separated metric list is efficient and immediately useful.

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 simple, read-only aggregation tool with one optional parameter and no output schema, the description covers the core purpose and returned metrics well. It leaves minor gaps around default behavior and time-window semantics, but an agent can invoke it correctly from this definition.

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 only parameter, days, has no schema description, so the description must carry the meaning. It does clarify that the parameter controls the 'last N days' window, but it does not mention the default of 30, acceptable ranges, or boundary behavior.

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 clearly states that this tool returns ticket totals for a recent period and enumerates the metrics: opened, resolved, open now, urgent, average resolution time, and breakdowns by priority and topic. It distinguishes an aggregate stats tool from ticket-listing or single-ticket retrieval tools by implication, but does not explicitly name a sibling alternative.

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 description implies this is the tool to use for aggregate ticket metrics over a time window, but it does not explicitly say when to prefer it over avarole_list_tickets or avarole_get_ticket. There are no exclusions, prerequisites, or alternative-routing instructions.

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