Sautikit

desk_create_ticket

Opens a SautiDesk ticket for a contact (contact_id) or a number/email (to). Nothing is sent: to message someone use desk_send_message and the ticket follows. If they already have an open ticket, that one is returned.

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

Input Schema

Name	Required	Description
`to`	No	phone number or email of who the ticket is for, when they are not yet a contact
`name`	No	the person's name, used when the contact is new
`extra`	No	optional additional fields
`channel`	No	optional ticket channel (call, sms, whatsapp, email)
`purpose`	No	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.
`subject`	No	optional ticket subject
`priority`	No	ticket priority (low, normal, high, urgent)
`queue_id`	No	optional queue UUID
`contact_id`	No	optional contact UUID
`assignee_id`	No	optional assignee user UUID
`category_id`	No	optional category UUID
`idempotency_key`	No	optional Idempotency-Key header

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations only declare openWorldHint=false and destructiveHint=false; the description adds genuinely new behavior: nothing is sent, and an existing open ticket is returned instead of a duplicate. It does not explain how the 12 optional fields interact (e.g., whether channel/priority are preserved when an existing ticket is reused), which keeps it from a 5.

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?

Three short sentences, zero filler, with the core action front-loaded and the dedup behavior last. Every sentence carries distinct information.

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?

With 12 all-optional params and no output schema, the description covers the two things an agent most needs: which identity fields select the recipient and what comes back when a ticket already exists. It leaves implicit that at least one of contact_id/to must be supplied, a minor gap given zero required params.

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%, so every parameter including the purpose/Pro-report note is already documented in the schema. The description adds only the identity-resolution idea (contact vs raw number/email), which the schema also states; baseline 3 applies.

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?

Uses a specific verb and resource ("Opens a SautiDesk ticket") and immediately names the two identity paths (contact_id or to). An agent can tell this apart from desk_send_message and desk_create_task from the description alone.

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?

Explicitly routes the agent: "to message someone use desk_send_message and the ticket follows," which is a clear when-to-use/when-not signal. It does not discuss choosing a ticket over a task (desk_create_task) or when to create a contact first, so it stops short of full alternative coverage.

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?