Skip to main content
Glama

Watch topic

watch_topic

Listens to a topic for a few seconds in read-only mode and returns observed messages so you can learn their shape before writing expect_message steps.

Instructions

Listen to a topic for a few seconds (read-only, from now on) and return the messages seen, to learn their shape before writing expect_message steps. Values are shown as sent; don't use it on topics carrying real personal data.

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": {
      "topic": "<topic>"
    },
    "name": "watch_topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
topicYes
brokerNo
secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it declares read-only behavior, a forward-only time window, and the important caveat that values are returned unmasked ('shown as sent'), which drives the privacy warning. It omits whether the call blocks for the full duration, what happens on an unknown topic or broker, and any rate limits, which keeps it short of a 5.

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, front-loaded with the action and its scope, followed by the output caveat and the privacy constraint. No filler, and the parenthetical 'read-only, from now on' compresses two behavioral facts into four words.

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?

There is no output schema and no annotations, so the description is the only source of behavioral detail; it covers the safety profile and time window well. However, for a tool whose entire purpose is inspecting message shape, it never says what the returned messages look like or how limit truncates them, and the broker/limit parameters remain opaque.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters, so the description must supply the meaning and it largely does not. 'A few seconds' loosely gestures at the seconds parameter, but limit, broker, and even topic are left entirely to the bare schema titles, and the interaction between seconds and limit is unstated.

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?

States a specific verb and resource ('listen to a topic'), the scope of the operation ('for a few seconds, from now on'), and the return ('the messages seen'). It also gives the agent the reason to call it ('learn their shape before writing expect_message steps'), which is far more actionable than the title alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ('before writing expect_message steps') and explicit when-not-to-use ('don't use it on topics carrying real personal data'), plus a temporal boundary that rules out historical replay ('from now on'). The listed siblings are unrelated tools, so no alternative routing is needed.

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