sprrint

sprrint_tasks_comment

Comment on tasks and reply to existing comments to capture feedback and maintain context within projects.

Instructions

Comment on a task. parent is an optional comment id for a reply.

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": {
      "key": "<key>",
      "body": "<body>"
    },
    "name": "sprrint_tasks_comment"
  }
}

Input Schema

Name	Required	Description	Default
`key`	Yes
`body`	Yes
`parent`	No
`project`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 30, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral disclosure burden. It only states the action and the parent parameter; it does not mention required permissions, effects, idempotency, error behavior, or return values for a mutating operation.

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?

The description is concise and front-loaded, with no unnecessary filler. It is a short, useful statement, though its brevity contributes to the lack of parameter and behavioral detail.

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 tool with 4 parameters, no annotations, and no output schema, the description is incomplete. It explains the core action and reply semantics but omits guidance on key/body/project meaning, return behavior, and side effects, leaving an agent with significant gaps.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for all four parameters. It only explains 'parent' as an optional comment id for a reply; 'key', 'body', and 'project' remain undocumented and are left to inference.

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?

The description clearly states the action ('Comment on a task') and the resource, making the purpose immediately understandable. It does not explicitly differentiate from sibling task tools like tasks_update or tasks_create, though the 'comment' verb is reasonably distinct.

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

Usage Guidelines4/5

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

The description gives clear context: use this tool to comment on a task, and use the parent parameter for replies. It does not explicitly state when not to use it or name alternatives, but the intended usage is clear enough for agent selection.

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

Deploy Server