Skip to main content
Glama
Sign In
Xalantis MCP Server

Xalantis MCP Server

Official
by xalantis-hub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_ticket_replies

Retrieve all replies and notes for a specific ticket to review conversation history and internal notes.

Instructions

List all replies and notes for a ticket

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_uuid": "<ticket_uuid>"
    },
    "name": "list_ticket_replies"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number
per_pageNoResults per page
ticket_uuidYesTicket UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits but only states 'list all replies and notes'. It does not mention that the operation is read-only, how pagination works (despite page/per_page in schema), or any ordering. The agent gains no safety or behavioral insight beyond the tool name.

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?

The description is a single sentence with no waste. It is front-loaded with the core purpose. However, it is so brief that it sacrifices useful context, preventing a maximum score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has no output schema, yet the description does not specify the return structure (e.g., fields in each reply, whether notes are included). For a list operation with 3 parameters, this omission leaves the agent uncertain about the response format, making it incomplete.

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 100%, so the schema already documents each parameter. The description adds no additional meaning or context about how parameters like 'ticket_uuid', 'page', or 'per_page' should be used, resulting in baseline score.

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 the verb 'list' and resource 'all replies and notes for a ticket', distinguishing it from sibling tools like 'reply_to_ticket' (create) and 'get_ticket' (view ticket details). However, it could be more precise by specifying that it includes both public replies and internal notes.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention scenarios where 'get_ticket' or 'reply_to_ticket' might be more appropriate, nor does it offer any exclusion criteria.

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