Skip to main content
Glama
avarole-mcp
by Sbaig3229

avarole_list_tickets

Read-only

List support tickets and filter them by status, priority, assignee, or search terms to find open issues, unassigned work, or tickets by requester.

Instructions

List support tickets. status: open (default: not resolved or closed), all, or one status. priority: urgent, high, normal or low. assigned_to: unassigned, a person's name, or their user id. search: words in the subject or requester.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
searchNo
statusNoopen
priorityNo
assigned_toNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely important behavior: the default status is 'open' meaning 'not resolved or closed', warning an agent that omitting status silently returns a filtered subset rather than everything.

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?

Front-loaded verb+resource followed by a tight per-parameter value list, with zero filler. The telegraphic style is efficient, though the dropped articles make the 'open' default clause slightly harder to parse than necessary.

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?

For a 5-parameter tool with no output schema and no schema descriptions, the definition covers most filtering semantics. It omits pagination/limit behavior and says nothing about result ordering or what a ticket record contains, which matters when no output schema exists.

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?

With 0% schema description coverage, the description carries the full burden and does most of it well, enumerating allowed values for status (open/all/any one status), priority (urgent/high/normal/low), assigned_to (unassigned/name/user id), and search scope (subject or requester). It leaves the limit parameter's meaning and the concrete set of status values (e.g. resolved, closed) undefined.

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?

Opens with a specific verb+resource ('List support tickets'), which cleanly separates it from avarole_get_ticket (single record) and avarole_ticket_stats. It does not name any sibling explicitly, so it stops short of full differentiation.

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?

Usage is implied by the filter list rather than stated: an agent can infer this is the tool for finding tickets by status/priority/assignee/keyword. There is no when-not-to-use guidance and no pointer to avarole_get_ticket or avarole_ticket_stats for follow-up needs.

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