Skip to main content
Glama

signal-bureau

by io.github.evolutionlabs-dev
OverviewDiscussionsAdmin

get_watch_feed

Read-onlyIdempotent

The structured daily delivery for a machine-watched topic: up to 14 days of observed items (title, url, source, date) newest-first, plus the topic's live coverage-acceptance report, which grades the coverage and shows the evidence (it does not gate billing — billing starts when the Watch starts, and the month you are in is refundable in full, any time you ask, for any reason). Delivery is pull: poll daily or on demand. Topics not yet watched: get_quote prices them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoHow many recent days to return (1-14, default 14)
sinceNoOptional. What changed since then: an ISO time (2026-10-01 or 2026-10-01T12:00:00Z) or the readingId a previous call returned. Adds a `delta` block listing the items first seen after it, by canonical address (a re-listed address is not new). States: compared, no-new, beyond-window (older than the 14-day window: unknown, not none), cannot-measure (names the pass that failed). Departures are never inferred. Omit it and the payload is unchanged.
topicYesThe watched topic name (as quoted/ordered)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / since
      Added value: +{
+  "description": "Optional. What changed since then: an ISO time (2026-10-01 or 2026-10-01T12:00:00Z) or the readingId a previous call returned. Adds a `delta` block listing the items first seen after it, by canonical address (a re-listed address is not new). States: compared, no-new, beyond-window (older than the 14-day window: unknown, not none), cannot-measure (names the pass that failed). Departures are never inferred. Omit it and the payload is unchanged.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive and non-open-world, yet the description adds substantial behavioral context beyond them: pull-based delivery rather than push, that the coverage grade does not gate billing, and the exact semantics of the optional delta comparison ('Departures are never inferred'). This is real value over structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with what is returned before the routing note, and most sentences earn their place. The billing/refund parenthetical is the weakest element — it explains a trust concern rather than invocation behavior — but it is contained and the overall length is justified for a tool with no output schema.

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?

With no output schema, the description carries the burden and does so: it enumerates returned item fields, states the 14-day window and ordering, describes the delta block and its failure states, and explains delivery mechanics. An agent has enough to call and interpret this correctly without further digging.

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 100%, and the schema itself exhaustively documents 'days' and 'since' (including the compared/no-new/beyond-window/cannot-measure states), so the description need not carry parameter meaning. The description adds only the 'up to 14 days / newest-first' framing, which is marginal beyond the schema, making 3 the correct baseline.

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+resource with scope: the structured daily delivery for a machine-watched topic, up to 14 days of items with named fields, plus the coverage-acceptance report. It also distinguishes itself from a sibling by routing unwatched topics to get_quote, so an agent can classify it without opening the schema.

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 a clear usage model ('Delivery is pull: poll daily or on demand') and an explicit alternative for one condition ('Topics not yet watched: get_quote prices them'). It does not contrast itself against other feed-like siblings such as get_desk_feed, todays_brief, or get_topic_record, so the routing is clear but not exhaustive.

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

All signal-bureau 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