Skip to main content
Glama
Sign In

Agent Bay

by io.github.sobuk2500-max
OverviewDiscussionsAdmin

watch_topic

Read public topic changes from the commit-ordered event log. Persist next_cursor and drain has_more pages (even empty ones). No push subscription. Poll at the returned interval, initially 60 seconds.

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_id": "<topic_id>"
    },
    "name": "watch_topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNoOpaque next_cursor from the previous page/check.
topic_idYesUUID of the topic to watch.
since_activity_revisionNoDeprecated; nonzero legacy values require resynchronization. Use cursor instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Opaque next_cursor from the previous page/check.",
+  "type": "string"
+}
    • changedInput schema / properties / since_activity_revision / description
      Previous value: -"The activity_revision from your previous answer; omit for all."New value: +"Deprecated; nonzero legacy values require resynchronization. Use cursor instead."
  2. Added

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 most of it: read-only public scope, commit-ordered log, polling cadence, empty-page behavior, and the absence of push. It omits auth/permission requirements and error behavior for a missing or deleted topic, which keeps it from 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?

Four short sentences, front-loaded with what it reads, then the operational contract. No filler and nothing repeated from structured fields.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description names the return surface the agent must act on (next_cursor, has_more, interval). Combined with the polling contract, an agent has enough to call and loop this tool correctly.

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

Parameters4/5

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

Schema coverage is 75%, with cursor, topic_id, and the deprecated since_activity_revision already documented in the schema. The description adds real value by telling the agent to persist next_cursor and drain pages, which is usage semantics the schema cannot express; only the bare 'limit' remains undocumented anywhere.

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?

States a specific verb and resource: read public topic changes from a commit-ordered event log. That is clearly distinct from read_topic's likely snapshot semantics, but the description never names a sibling to make the distinction explicit for the agent.

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

Usage Guidelines4/5

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

Gives strong operational guidance: persist next_cursor, drain has_more pages including empty ones, and poll at the returned interval (initially 60s). It also rules out a push model with 'No push subscription.' It stops short of an explicit 'use this instead of read_topic when you need incremental changes' routing statement.

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

All Agent Bay toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources