Skip to main content
Glama

signal-bureau

by io.github.evolutionlabs-dev
OverviewDiscussionsAdmin

unfurl_watch

Read-onlyIdempotent

Watches: configure and unfurl free; saving is the paid step. Configure a Watch and run it once, without saving: the governed reading (sb.watch-reading.v1) plus a line per coordinate saying whether it was applied. Free, as often as you like; no key. Either start from a standard Watch (base; these read the Strait of Hormuz record) or name your own domain (domain + topics, from get_quote). For a domain, the coverage check runs again here and only covered topics are kept; no reading builder is published for this domain yet, so its reading is cannot-measure per topic and it is never served a standard Watch's reading. Same content as POST /api/v1/watches/unfurl.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
baseNoThe standard Watch to start from: std.hormuz.maritime-operator, std.hormuz.energy-desk, std.us-iran.geopolitical-analyst. Leave it out when you name a domain.
domainNoYour domain in your own words, e.g. Arizona startup ecosystem. Use with topics instead of base.
expandNoOverride the Watch's depth for this call: 0, 1, 2 ... or full.
topicsNoThe topics your domain splits into (get_quote proposes them), as names or {name, scope}; 1 to 40. Only the ones coverage we keep reads are kept; the rest come back as free coverage requests.
quoteIdNoThe quoteId get_quote returned. Recorded with the Watch; the coverage is checked again here either way.
coordinatesNoThe coordinates you want to change from the base Watch; every one you leave out takes the base Watch's value. Keys: observer, question, domain, interval, language, depth, cadence, selection, thresholds, permission, delivery. Today the reading honours depth and delivery; the rest are recorded on your Watch and stated as not yet applied.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / base / description
      Previous value: -"The standard Watch to start from: std.hormuz.maritime-operator, std.hormuz.energy-desk, std.us-iran.geopolitical-analyst."New value: +"The standard Watch to start from: std.hormuz.maritime-operator, std.hormuz.energy-desk, std.us-iran.geopolitical-analyst. Leave it out when you name a domain."
    • addedInput schema / properties / domain
      Added value: +{
+  "description": "Your domain in your own words, e.g. Arizona startup ecosystem. Use with topics instead of base.",
+  "type": "string"
+}
    • addedInput schema / properties / quoteId
      Added value: +{
+  "description": "The quoteId get_quote returned. Recorded with the Watch; the coverage is checked again here either way.",
+  "type": "string"
+}
    • addedInput schema / properties / topics
      Added value: +{
+  "description": "The topics your domain splits into (get_quote proposes them), as names or {name, scope}; 1 to 40. Only the ones coverage we keep reads are kept; the rest come back as free coverage requests.",
+  "items": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "properties": {
+          "name": {
+            "type": "string"
+          },
+          "scope": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name"
+        ],
+        "type": "object"
+      }
+    ]
+  },
+  "type": "array"
+}
    • removedInput schema / required
      Removed value: -[
-  "base"
-]
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description adds real behavior: no auth key required, unlimited free re-runs, the coverage check re-running and dropping uncovered topics, and a custom domain yielding cannot-measure per topic and never inheriting a standard Watch's reading. It does not contradict the annotations and adds meaningful operational context.

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

Conciseness3/5

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

The lead sentence front-loads the free/paid distinction, which is good, but the rest is a run-on sequence of clauses with inconsistent punctuation and phrasing. Several sentences (coverage-check, cannot-measure, never-served-reading chain) could be tightened without losing meaning.

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?

With no output schema, the description usefully sketches the return shape (a governed reading plus a per-coordinate applied line) and covers both branch cases for a 6-param optional-everything tool. Remaining gaps are minor, such as the exact reading payload or error behavior on a missing get_quote step.

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 the schema already documents base, domain, topics, quoteId, expand and coordinates keys. The description reinforces a few semantics (domain paired with topics, quoteId recording, coordinates being re-checked here) but adds little beyond the schema text, so the 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 states a concrete verb+resource: configure a Watch and run it once without saving, returning the sb.watch-reading.v1 reading. It implicitly contrasts with the saving path ('saving is the paid step'), which maps to the save_watch sibling. The prose is convoluted and fragmented, but an agent can still tell what the tool does.

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?

It gives explicit context: free, unlimited, no key, and two mutually exclusive entry paths (base standard Watch vs. domain + topics from get_quote). It stops short of a clean when-not statement or naming save_watch as the alternative for persistence, so it falls just short of 5.

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