Sautikit

desk_create_task

Creates a SautiDesk follow-up task.

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

Input Schema

Name	Required	Description
`notes`	No	optional task notes
`title`	Yes	task title
`due_at`	No	optional ISO-8601 due timestamp
`lead_id`	No	optional lead UUID: makes this a follow-up on that lead
`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.
`ticket_id`	No	optional linked ticket UUID
`assignee_id`	No	optional assignee user UUID
`remind_minutes`	No	optional minutes before due to remind (the type's default otherwise)
`activity_type_id`	No	optional activity type UUID: what the follow-up is

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 6, 2026

addedInput schema / properties / activity_type_id

Added value: +{
+  "description": "optional activity type UUID: what the follow-up is",
+  "type": "string"
+}

addedInput schema / properties / lead_id

Added value: +{
+  "description": "optional lead UUID: makes this a follow-up on that lead",
+  "type": "string"
+}

addedInput schema / properties / remind_minutes

Added value: +{
+  "description": "optional minutes before due to remind (the type's default otherwise)",
+  "type": [
+    "null",
+    "integer"
+  ]
+}

First observedNov 5, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations only declare the safe defaults (destructiveHint=false, openWorldHint=false); the description adds nothing beyond "creates". It says nothing about whether the task is assigned to the caller by default, whether a reminder fires, whether the linked lead/ticket is notified, or how due_at behaves when omitted.

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 short, front-loaded sentence with no filler. It is efficient, though the brevity is achieved by omission rather than by tight phrasing of real content.

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

Completeness2/5

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

This is a nine-parameter creation tool with no output schema, so the description must carry more weight. It leaves the agent without the create semantics (defaults, assignment, reminders) needed to call it confidently beyond the schema.

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% and each of the nine parameters is documented in the schema, so the baseline applies. The description could have clarified the relationship between lead_id, ticket_id and assignee_id, but it adds no parameter meaning at all.

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 ("Creates a SautiDesk follow-up task"), which cleanly separates it from desk_create_ticket and desk_create_lead. It does not explicitly name the update/list siblings, so sibling differentiation is only implicit.

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?

There is no guidance on when to create a task versus logging an activity (desk_log_activity), updating a ticket, or adding a note. The word "follow-up" hints at use but the agent gets no prerequisites or alternatives.

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?