Skip to main content
Glama
Sign In
Support Ticket Triage MCP

Support Ticket Triage MCP

by MatiasLaukka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_audit_events

Read-onlyIdempotent

Retrieve audit events from support ticket triage, optionally filtered by ticket ID, to review actions taken.

Instructions

Read all audit events or events for one ticket.

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": "get_audit_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
ticketIdNo

Output Schema

NameRequiredDescriptionDefault
limitYes
totalYes
eventsYes
offsetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the scoping to one ticket but does not disclose pagination behavior, ordering, or what happens when ticketId is omitted.

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 description is a single, front-loaded sentence with no unnecessary words. It efficiently communicates the core functionality.

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?

The tool has an output schema and safety annotations, so basic use is covered. However, the description is minimal for a paginated read tool with an optional filter; it does not explain pagination or the precise behavior when ticketId is missing, leaving some gaps.

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?

The schema has 0% description coverage, so the description must compensate. It only hints at ticketId via 'one ticket' and does not explain limit or offset semantics. The parameter names are somewhat self-explanatory, but the description lacks explicit mapping and context for all three parameters.

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

Purpose5/5

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

The description clearly identifies a read operation for audit events, with explicit scope: all events or events for one ticket. This distinguishes it from sibling tools like get_ticket or list_tickets, which operate on tickets, not audit events.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of audit trail use cases, prerequisites, or exclusions, leaving the agent without explicit decision support.

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

Deploy Server

Other Tools