Skip to main content
Glama

Watch a Jobs card in a room

watch_room_todo
Idempotent

Subscribes a chat room to a Jobs card and posts a single line when the card's material state changes.

Instructions

Subscribes a Chat room to one Jobs card. The scheduled room watcher posts a single line only when the card's material state changes.

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": {
      "thread_id": "<thread_id>",
      "todo_id": "<todo_id>"
    },
    "name": "watch_room_todo"
  }
}

Input Schema

NameRequiredDescriptionDefault
todo_idYesJobs card UUID.
thread_idYesChat thread UUID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already convey that this is an idempotent, non-destructive write. The description adds valuable context: a scheduled watcher posts a single line only on material state change. It does not cover auth or rate limits, but the added behavioral detail is substantial.

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 sentences with zero waste. The action is front-loaded and the second sentence adds behavioral nuance without redundancy.

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?

Annotations cover safety and idempotency, and the description explains the effect of the call. It does not mention how to remove the watch or any side effects outside the card's state changes, but for a simple subscription tool it is nearly 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 coverage is 100%, so both parameters are fully documented. The description mentions 'a Chat room' and 'one Jobs card' which map to the schema parameters, but adds no syntax or format details beyond what the schema provides. Baseline 3 applies.

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 uses a specific verb ("Subscribes") and resource ("a Chat room to one Jobs card"), making the action clear. However, it does not explicitly contrast with siblings like list_room_watches or post_room_update, so it falls just 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 implies usage by explaining the effect (subscription to a card), but it does not state when to use this tool versus alternatives or any prerequisites. It leaves the agent to infer the context.

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