Dutify

pm_remove_comment_reaction

Destructive

Remove a reaction by identifier. Only the user who added the reaction may remove it. 204. API-key scope: tasks:write.

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": {
      "taskIdentifier": "<taskIdentifier>",
      "commentIdentifier": "<commentIdentifier>",
      "reactionIdentifier": "<reactionIdentifier>"
    },
    "name": "pm_remove_comment_reaction"
  }
}

Input Schema

Name	Required	Description
`account`	No	Multi-account auth only: name of the account from X-Dutify-Accounts to use for this call. Ignored in single-account mode (X-API-Key header). When multiple accounts are configured and this is omitted, the call fails with ACCOUNT_REQUIRED listing the available names. list_accounts never requires a selection.
`workspace`	No	Workspace identifier or exact name for this call. Overrides the configured workspace. For personal keys, discover candidates with list_workspaces and select explicitly. Does not change other calls or expand a workspace key's access.
`taskIdentifier`	Yes	Task identifier (tsk_…)
`commentIdentifier`	Yes	Comment identifier (cmt_…)
`reactionIdentifier`	Yes	Reaction identifier (react_…)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 24, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Goes beyond the annotations by disclosing the ownership authorization requirement, the 204 no-content response, and the required `tasks:write` API-key scope. The annotations already carry destructiveHint=true and idempotentHint=false, so the description's job is to add operational detail — which it does. It does not say what happens when the reaction is missing or owned by someone else.

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, front-loaded with the action, then the authorization constraint, then the response code and scope. Every sentence carries distinct information with no filler.

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

Completeness4/5

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

For a destructive, permission-gated mutation with no output schema, the definition covers the mutation, the auth requirement, the scope string, and the empty 204 return. It omits error behavior (403 when not the owner, 404 when the reaction is absent), which is the main remaining gap.

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%, so all five parameters including account/workspace scoping are already fully documented in the schema. The description only restates that removal is 'by identifier' and adds no format or interaction detail beyond that, which is the baseline when the schema does the heavy lifting.

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 ('Remove a reaction') plus how it is addressed ('by identifier'), which distinguishes it in practice from pm_add_comment_reaction and pm_list_comment_reactions. It never names a sibling explicitly, so it stops short of the top mark.

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 description gives an ownership precondition ('Only the user who added the reaction may remove it'), which is a real gating rule rather than pure usage guidance. It offers no explicit when-to-use/when-not-to-use framing or named alternatives, leaving the agent to infer that add/list reactions are separate tools.

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

All Dutify 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?