Skip to main content
Glama

List room card watches

list_room_watches
Read-onlyIdempotent

Lists the Jobs cards currently watched by a Chat room so you can see which cards are being monitored for a given chat thread ID.

Instructions

Lists the Jobs cards currently watched by a Chat room.

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>"
    },
    "name": "list_room_watches"
  }
}

Input Schema

NameRequiredDescriptionDefault
thread_idYesChat thread UUID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only that results reflect cards 'currently' watched by a Chat room, and does not disclose auth requirements, pagination, ordering, or empty-room behavior.

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 front-loaded sentence with no filler. That is appropriately sized for a simple list operation.

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?

For a simple read-only list with a fully documented single parameter and explicit safety annotations, the description is largely sufficient. A minor gap is that it does not indicate return ordering, pagination, or what a watch record contains, though there is no output schema to rely on.

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%, and the single parameter is documented as a 'Chat thread UUID.' The description's phrase 'Chat room' helps map thread_id to the room scope, but it adds no format or semantic details beyond what the schema already provides.

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 states a specific verb ('Lists') and resource ('Jobs cards currently watched by a Chat room'), matching the tool name and title. It does not explicitly distinguish this from sibling watch-related tools such as watch_room_todo, so it falls short of the top score.

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?

The description provides no when-to-use, when-not-to-use, or alternative-tool guidance; an agent must infer usage from the verb and scope. It also does not mention conditions such as needing a valid thread_id or when to choose this over other room-related tools.

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