Skip to main content
Glama
avarole-mcp
by Sbaig3229

avarole_team_workload

Read-only

Shows how many live support tickets each person and group holds, plus how many remain unassigned.

Instructions

Who is holding how many live tickets, per person and per group, and how many nobody has taken.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

Annotations already declare this a safe, closed-world read (readOnlyHint=true, openWorldHint=false), so the safety profile is covered. The description adds the scope of what is aggregated, but does not define what counts as 'live' (status filter, age), whether results are ordered, or anything about the response shape, which would matter on a tool with no output schema.

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, and the key output dimensions (per person, per group, unassigned) are front-loaded. The conversational question phrasing is slightly informal but costs no space.

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 zero-parameter, read-only aggregation tool with no output schema, the description conveys the unit of measure and grouping levels, which is enough to call it correctly. The main residual gap is that the term 'live' is never defined, so the agent cannot know which ticket states are included.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. It correctly signals that no filtering arguments are needed.

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 a specific resource (live tickets) and the exact breakdown it returns: per person, per group, and the unassigned count. That is far more informative than a generic 'team workload' label and distinguishes it in spirit from aggregate siblings like avarole_ticket_stats, though no sibling is 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?

The framing as a question ('Who is holding how many...') implies the use case of checking distribution or finding unassigned work, but there is no explicit when-to-use statement, no exclusions, and no pointer to avarole_ticket_stats or avarole_list_tickets as alternatives.

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