Sautikit

desk_list_tickets

Read-only

Lists SautiDesk tickets with optional filtering by status, priority, channel, assignee, queue, contact, or search query.

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": {
      "purpose": "<purpose>"
    },
    "name": "desk_list_tickets"
  }
}

Input Schema

Name	Required	Description
`q`	No	optional search query
`limit`	No	optional page size (default and max 100)
`cursor`	No	next_cursor from the previous page
`status`	No	optional ticket status filter (e.g. open, pending, resolved, closed)
`channel`	No	optional channel filter (voice, sms, whatsapp, email, webchat)
`purpose`	Yes	Required on tools that read data or reports; recommended on every tool. One sentence: what you are doing and why (for example "finding this caller's open ticket to answer them"). Building a report, dashboard, analytics or an export is a SautiDesk Pro feature done by the report tools, not by pulling records.
`priority`	No	optional priority filter (low, normal, high, urgent)
`queue_id`	No	optional queue UUID
`contact_id`	No	optional contact UUID
`assignee_id`	No	optional assignee user UUID

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

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, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only that filters are optional; it says nothing about default ordering, page-size behavior, or what the result set contains, which would be the value-add beyond annotations.

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?

One front-loaded sentence naming the resource first, then the optional filters. Zero filler, though the filter enumeration partially duplicates the schema and could be trimmed without losing meaning.

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 10-parameter list tool with no output schema, the description covers purpose and filter scope but omits pagination behavior (limit/cursor) and the mandatory 'purpose' argument's significance, both of which an agent needs to call it correctly across pages.

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 every filter's meaning and accepted values are already documented in the schema. The description merely restates the filter list without adding format, matching, or combination semantics (e.g. whether filters AND together), so the baseline 3 applies.

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?

States a specific verb and resource ("Lists SautiDesk tickets") and enumerates the filter dimensions, which distinguishes it from desk_get_ticket and desk_list_tasks by implication. It stops short of explicitly naming the sibling to use for a single ticket or for other record types.

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 phrase "with optional filtering by..." implies the browse/filter use case, but there is no explicit when-to-use or when-not guidance, no mention of paging through results with cursor, and no routing to desk_get_ticket for single-record lookups.

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

All Sautikit 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?