Skip to main content
Glama
Sign In

Sautikit

by io.github.SautiKit
OverviewDiscussionsAdmin

desk_add_ticket_comment

Adds an internal agent note/comment to a SautiDesk ticket.

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": {
      "activity_id": "<activity_id>",
      "body": "<body>"
    },
    "name": "desk_add_ticket_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesinternal team comment text (customers never see it)
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.
activity_idYesUUID of the message or call to comment on (an item on the ticket timeline)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations declare destructiveHint=false and openWorldHint=false but omit readOnlyHint, so the agent must infer that this appends data. The description confirms an additive 'adds' action and that the note is internal, which is useful, but says nothing about notification side effects, immutability of posted comments, or required permissions. It also loosely says comments go 'to a SautiDesk ticket' while the schema targets a specific timeline activity.

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?

A single short sentence with the action and resource front-loaded and no filler. Nothing could be removed 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 three-parameter append operation with full schema coverage and no output schema, the essentials are present, but the description never states what comes back (e.g., the created comment object or its ID) or whether the caller must belong to the ticket. That leaves minor gaps for correct invocation and follow-up.

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 all three parameters are already documented, including that `body` is customer-invisible and `activity_id` is a timeline item UUID. The description adds no syntax, format, or constraint detail beyond the schema, so the baseline of 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 plus resource ('Adds an internal agent note/comment') scoped to a ticket, which cleanly separates it from read-side siblings like desk_list_activity_comments and customer-facing desk_send_message. It stops short of explicitly naming those alternatives, so the differentiation is inferred rather than stated.

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 word 'internal' implies this is for staff-only notes rather than customer-visible replies, which gives an implicit usage cue. However, there is no explicit when-to-use/when-not-to-use guidance, no mention of alternatives such as desk_send_message for customer replies, and no stated prerequisites.

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