Saga MCP

Overview Schema Source Related Servers Discussions Admin

comment_delete

Idempotent

Remove a comment while preserving an audit trail. Hides it from lists and task views to retract incorrect or stale feedback. Restorable if needed.

Instructions

Remove a comment (soft delete). The row is kept for the audit trail but hidden from comment_list and task_get. Use this to retract a comment that turned out to be wrong or stale. Reversible with comment_restore.

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

Input Schema

Name	Required	Description
`id`	Yes	Comment ID to remove
`reason`	No	Why the comment is being removed (recommended — it stays in the audit trail)
`deleted_by`	No	Who removed it (optional)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.10.0Sep 6, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes well beyond the annotations by revealing that the row is retained for the audit trail, is hidden from listing/reading operations, and can be restored. This is exactly the kind of non-obvious behavioral context that annotations alone do not capture.

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 with no wasted words. The core behavior is front-loaded, followed by the key consequence and the recovery path. Every sentence earns its place.

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

Completeness5/5

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

Given the simple 3-parameter, no-output-schema tool, the description covers the operation's effect, visibility changes, audit implications, and reversibility. Nothing essential is missing for an agent to invoke this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents all three parameters at 100% coverage, so the baseline is 3. The description adds meaningful context for the 'reason' parameter by noting it stays in the audit trail, which deepens the agent's understanding of what to supply and why.

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?

Description states a specific verb ('Remove'), a specific resource ('a comment'), and clarifies that this is a soft delete with concrete visibility consequences (hidden from comment_list and task_get). It clearly distinguishes this from comment_add and comment_restore even without exploring schemas.

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

Usage Guidelines5/5

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

Explicitly says to use this to retract a comment that is wrong or stale, and names the recovery alternative ('Reversible with comment_restore'). This gives the agent clear selection criteria between the delete and restore operations.

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