Skip to main content
Glama
avarole-mcp
by Sbaig3229

avarole_get_ticket

Read-only

Retrieve a single support ticket by ID, including customer messages, replies, private notes, and recent activity to review the full conversation and context.

Instructions

One ticket with its conversation (customer messages, replies, private notes) and recent activity.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticket_id": "<ticket_id>"
    },
    "name": "avarole_get_ticket"
  }
}

Input Schema

NameRequiredDescriptionDefault
ticket_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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's added value is disclosing the return contents — customer messages, replies, private notes, and recent activity — which matters since there is no output schema; it stops short of noting behavior when a ticket is missing or who may see private notes.

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 compact sentence that front-loads the resource and then enumerates the payload. No redundant or filler wording, though the sentence-fragment form makes the action implicit.

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 one-parameter read tool with no output schema, describing the returned payload is the key completeness requirement and it does that. It leaves gaps around not-found behavior, permissions on private notes, and the meaning of ticket_id, which a slightly richer description could cover.

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?

Schema description coverage is 0%, so the description would ideally explain ticket_id, but it says nothing about the parameter. The lone parameter is a self-explanatory integer identifier, which limits the practical damage, so this lands at the minimum-viable level rather than below it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource and its scope (a single ticket plus its conversation and recent activity), which implicitly contrasts with the list_tickets sibling. However, it is a bare noun phrase with no verb and never explicitly states retrieval or differentiates itself from alternatives by name, so the agent must infer the operation.

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, no mention of prerequisites such as needing a known ticket_id, and no reference to sibling tools like avarole_list_tickets for discovery. The single-ticket framing hints at usage but nothing is stated.

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