Skip to main content
Glama
Sign In
ticksy-mcp

ticksy-mcp

by artkrsk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_open_tickets

List all open support tickets, optionally filtering to only those awaiting a customer reply.

Instructions

List open tickets (summary). Use get_ticket for full details.

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

Input Schema

NameRequiredDescriptionDefault
needs_response_onlyNoIf true, return only tickets where the customer is waiting for a reply

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It implies a read-only operation ('list') and is open about returning only a summary, but it does not explicitly state whether it's read-only or mention any side effects. Adequate for a simple list tool.

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?

Extremely concise at two sentences, with no redundant words. The purpose and key guidance are front-loaded. Every sentence earns its place.

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

Completeness4/5

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

Given no output schema, the description hints at the return type ('summary'), which is adequate for a simple list operation. However, it could be more explicit about what is returned (e.g., list of IDs or titles). Still, it's mostly complete for the complexity level.

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 coverage is 100% with one parameter fully described in the schema. The description adds no additional meaning to the parameter beyond what the schema provides, so baseline score is appropriate.

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 states the action (list) and resource (open tickets) with the qualifier 'summary', which distinguishes it from get_ticket. The purpose is unambiguous and specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides an explicit alternative (get_ticket for full details), guiding when not to use this tool. However, it does not differentiate from sibling tools like list_closed_tickets or list_my_tickets, which limits guidance.

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