Skip to main content
Glama
Sign In
@illodev/taiga-mcp

@illodev/taiga-mcp

by illodev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

taiga_issues_unwatch

Stop receiving notifications for a specific Taiga issue by removing its watcher status. Use this to declutter your issue list and focus on relevant tasks.

Instructions

Stop watching an issue.

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_issues_unwatch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIssue ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.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 behavioral disclosure. It only states the action without mentioning side effects, reversibility, permission requirements, or the fact that it's a mutating operation. This is a minimal gap in transparency.

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?

The description is a single, four-word sentence that is front-loaded and contains no waste. Every word earns its place for the simple action.

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?

Given the simple one-parameter schema and no output schema, the description conveys the core function but lacks context about behavior, return values, or usage conditions. It is minimally viable but not richly complete.

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% for the single 'id' parameter, which is described as 'Issue ID'. The description adds no additional meaning beyond the schema, so it sits at the baseline.

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?

The description 'Stop watching an issue' clearly states the action (stop watching) and the resource (an issue). It is specific and distinguishes this tool from sibling unwatch tools by limiting to issues.

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 implies usage when the user wants to stop watching an issue, but does not provide explicit guidance on when to use this tool versus alternatives like taiga_projects_unwatch or taiga_tasks_unwatch. The context is clear but no exclusions or alternative tools are mentioned.

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

Deploy Server

Other Tools