Skip to main content
Glama
MCP Connect Starter

MCP Connect Starter

by cdtalley

list_tickets

Retrieve support tickets in newest-first order and filter by open, pending, or closed status to review and prioritize incoming support requests.

Instructions

List support tickets, newest first, optionally filtered by status (open/pending/closed).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
statusNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It usefully states the default sort order ('newest first') and enumerates the legal status values, which the schema does not, but it says nothing about the default page size, pagination behavior, or how an unrecognized status is handled.

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?

A single sentence that front-loads the resource, then the ordering, then the filter. Every clause adds distinct information and there is no filler.

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 is simple and has an output schema, so return values need no explanation. However, for a list endpoint the omission of limit/pagination semantics is a genuine gap that leaves the agent unable to reason about result volume.

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 must compensate and it only half does: it enumerates status as open/pending/closed (a meaningful addition, since the schema types it as a bare string) while the 'limit' parameter is never mentioned and its default of 20 is left to the schema.

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 verb (list) and resource (support tickets) and adds ordering ('newest first') and an optional filter, so an agent knows exactly what it retrieves. It does not distinguish itself from sibling read tools such as get_ticket, which is the only missing piece for a 5.

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 'list ... optionally filtered' — an agent can infer this is the browse/enumerate endpoint. There is no explicit when-to-use versus get_ticket, and no stated condition for choosing a status value, so guidance stays at the implied level.

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