Skip to main content
Glama
talhaorak

Taiga MCP Bridge

by talhaorak

unwatch_item

Stop watching a specific Taiga item (user story, task, issue, epic, milestone, or wiki page) by providing its type and ID. Uses default session if not provided.

Instructions

Stop watching an item. object_type: 'user_story', 'task', 'issue', 'epic', 'milestone', or 'wiki_page'. Uses default session if session_id not provided.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
object_idYes
object_typeYes
session_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided. Description mentions default session behavior but lacks specifics on side effects, permissions, or response. Minimal disclosure beyond basic action.

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?

Two highly concise, front-loaded sentences with no redundancy. Every word adds value.

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?

With 3 params and 0% schema coverage, description explains 2 of 3 parameters partially. Lacks detail on object_id. Output schema exists but description doesn't reference it. Adequate but incomplete.

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 0%, so description must add meaning. It lists valid object_type values and notes session default, but does not explain object_id or provide format/constraints. Partial improvement over schema.

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 clearly states 'Stop watching an item' with specific object types listed. Distinct from sibling 'watch_item'.

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 on when to use this tool vs alternatives like 'watch_item' or other item actions. No context on prerequisites or conditions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/talhaorak/pytaiga-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server