Sautikit

desk_create_queue

Creates a new SautiDesk queue (requires desk.admin).

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

Input Schema

Name	Required	Description
`name`	Yes	queue name
`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.
`strategy`	No	ring strategy (e.g. ring_all, round_robin, least_recent)
`description`	No	optional queue description

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare openWorldHint=false and destructiveHint=false, so the safety profile of this create operation is covered. The description adds genuinely useful context beyond that: the desk.admin permission requirement. It does not say what happens on a duplicate name, whether strategy has a default, or what identifier comes back, which matters for a mutation tool.

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?

A single front-loaded sentence with zero filler, and the permission requirement is placed where an agent will see it immediately. It is arguably too sparse rather than padded, so it loses a point for what is absent rather than for wasted wording.

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?

With four documented parameters and no output schema, the structured fields carry most of the load, and annotations cover the safety profile. What is missing is the outcome an agent needs for a create call: whether the new queue's id/object is returned and how name collisions are handled.

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%, with meaningful per-field descriptions including the strategy examples and the purpose-field policy, so the baseline is 3. The description itself adds no parameter meaning; it never mentions name, strategy, or purpose.

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 ('Creates') and resource ('SautiDesk queue'), which lets an agent distinguish it from desk_list_queues and the other desk_* creation tools. It stops short of explicitly naming the read-side sibling, but the verb+resource pair is unambiguous.

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

Usage Guidelines2/5

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

The only guidance is the parenthetical '(requires desk.admin)', which is a prerequisite rather than a when-to-use rule. Nothing tells the agent when to create a queue versus using an existing one, or whether queues must precede ticket routing setup.

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?