@illodev/taiga-mcp

taiga_epics_watch

Monitor a specific Taiga epic by its ID. Get notified of changes, comments, and status updates to stay informed on its progress.

Instructions

Watch an epic.

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": "taiga_epics_watch"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Epic ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

C2.5/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of disclosing behavior, but 'Watch an epic' does not state that this is a state-changing operation, that it likely adds the current user as a watcher, whether permissions are required, or what the response looks like. The behavioral profile is essentially undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short and front-loaded, with no wasted words. However, it is under-specified to the point of being minimally informative, so while concise, it is not an appropriately sized description for a tool with no annotations or output schema.

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 no annotations and no output schema, the description should explain the effect, return value, and any prerequisites or side effects. 'Watch an epic' only names the action and resource, leaving an agent without enough context to predict the outcome or handle success/failure cases.

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?

The input schema fully describes the single parameter 'id' as 'Epic ID' with 100% coverage, so the description adds no additional parameter semantics. The baseline of 3 applies because the schema is sufficient and the description does not need to compensate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description specifies a verb ('Watch') and a resource ('an epic'), so it is clear this action applies to epics. However, it is essentially a restatement of the tool name with no explanation of what 'watching' means in this context (e.g., subscribing to notifications), making it vague for an agent unfamiliar with Taiga terminology.

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?

No guidance is provided about when to use this tool versus alternatives such as taiga_epics_unwatch, taiga_epics_watchers, or similar watch tools for other resource types. The description gives no context, prerequisites, or exclusions, so an agent cannot determine appropriate usage conditions.

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

Deploy Server