Kamaan

List Support Tickets

Support_List_Tickets

List support conversations across all products, newest first, with bucket, status and whether a draft is waiting. Filter by product, bucket, status or text.

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

Input Schema

Name	Required	Description	Default
`page`	No
`query`	No	Text to match in subject, customer or snippet.
`bucket`	No
`status`	No		open
`product_id`	No
`needs_human`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

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 must carry the full behavioral burden, and it does disclose sort order (newest first) and returned fields, which is useful. However, it omits that status defaults to "open" — so a default call silently excludes resolved and pending tickets — and says nothing about pagination size or what a page returns, both material for a paginated 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?

Two short sentences with zero filler, front-loading sort order and returned fields before the filter list. Every clause corresponds to something the agent needs.

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 six-parameter, unannotated, output-schema-less listing tool this is only partially sufficient: pagination behavior, the `needs_human` flag, and the open-by-default status filter are all unaddressed. The basics are covered, but an agent could call it and be surprised by results.

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 only 17%, so the description needs to compensate. It maps four filters (product, bucket, status, text) to parameter names the schema already enumerates, but leaves `page` and `needs_human` completely undiscussed and adds no format or semantics beyond the bare parameter names.

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 and resource ("List support conversations") and adds scope (all products, newest first) plus the fields returned (bucket, status, draft waiting). It implicitly separates itself from Support_Read_Ticket by listing across all products rather than reading one, but it never names that sibling, so differentiation is inferred rather than stated.

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?

The second sentence ("Filter by product, bucket, status or text") describes capability rather than when to choose this tool over Support_Read_Ticket or Support_Set_Status. Usage is implied by the verb "List", but there are no exclusions, prerequisites, or alternatives named.

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

All Kamaan tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?