signal-bureau

unfurl_watch

Read-onlyIdempotent

Watches: configure, unfurl and save free. 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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "unfurl_watch"
  }
}

Input Schema

Name	Required	Description
`base`	No	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.
`domain`	No	Your domain in your own words, e.g. Arizona startup ecosystem. Use with topics instead of base.
`expand`	No	Override the Watch's depth for this call: 0, 1, 2 ... or full.
`topics`	No	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.
`quoteId`	No	The quoteId get_quote returned. Recorded with the Watch; the coverage is checked again here either way.
`coordinates`	No	The 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.

Changed5 schema fields changedOct 6, 2026

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"
-]
```

AddedOct 5, 2026

TDQS

A4/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior. The description adds substantial context beyond them: no key/free usage, no saving, coverage re-check, only covered topics kept, domain readings are cannot-measure and never inherit a standard Watch reading, and output shape.

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 description is information-dense but not tightly structured; the opening 'Watches: configure, unfurl and save free' is awkward and some clauses repeat schema text. It front-loads the core preview behavior, but could be shorter.

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 six-parameter, nested, no-output-schema tool, the description covers the return shape, free/no-key access, base vs domain paths, and domain coverage limitations. It is largely complete, with minor ambiguity around the 'save free' phrasing and no explicit error cases.

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 all six parameters. The description reinforces base/domain/topics/coordinates behavior but adds little parameter-level meaning beyond the schema, so baseline 3 is appropriate.

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 action: configure a Watch and run it once without saving, returning a governed reading plus per-coordinate application lines. It distinguishes this preview from saving via 'without saving' and from standard Watch use via base/domain paths, though the opening 'configure, unfurl and save free' is slightly muddled.

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 clear usage paths: start from a standard Watch with base or name a domain with domain+topics from get_quote. It also notes the operation is free and repeatable, but it does not explicitly say to use save_watch when persistence is desired or list exclusions.

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

All signal-bureau tools Inspect

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

Need Help?