Skip to main content
Glama
Sign In

Sautikit

by io.github.SautiKit
OverviewDiscussionsAdmin

desk_update_task

Updates or completes a SautiDesk 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": {
      "task_id": "<task_id>"
    },
    "name": "desk_update_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoupdated title
due_atNoupdated ISO-8601 due timestamp
statusNoupdated status (open, completed)
purposeNoRequired 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.
task_idYestask UUID
outcome_idNowith status done: the outcome of a lead follow-up (logs the activity and moves the lead)
assignee_idNoupdated assignee user UUID
remind_minutesNoupdated reminder minutes before due
activity_type_idNoupdated activity type UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / activity_type_id
      Added value: +{
+  "description": "updated activity type UUID",
+  "type": "string"
+}
    • addedInput schema / properties / outcome_id
      Added value: +{
+  "description": "with status done: the outcome of a lead follow-up (logs the activity and moves the lead)",
+  "type": "string"
+}
    • addedInput schema / properties / remind_minutes
      Added value: +{
+  "description": "updated reminder minutes before due",
+  "type": [
+    "null",
+    "integer"
+  ]
+}
  2. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only the notion that a task can be completed as well as updated, but says nothing about partial-update semantics or the side effect of logging an activity and moving a lead when status is completed.

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 no filler or redundancy. It is efficient, though the brevity comes at the cost of the guidance scored elsewhere.

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?

For a 9-parameter mutation tool, one sentence is thin; an agent must read the schema to learn that only task_id is required and everything else is optional. The absence of any note on completing a task versus editing fields leaves behavior to be reverse-engineered.

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%, including the meaning of outcome_id and the purpose field, so the schema already carries parameter meaning. The description adds nothing beyond it, making the baseline 3 appropriate.

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 ("Updates or completes a SautiDesk task") and hints at the completion path, which partially separates it from desk_create_task and desk_update_ticket. It never names those siblings, so the agent still has to infer which task tool to pick.

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 explicit guidance on when to use this versus desk_create_task, desk_list_tasks or desk_update_ticket, and no prerequisites or exclusions. The only usage signal is the word "completes" implying status changes.

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

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