Skip to main content
Glama

signal-bureau

by io.github.evolutionlabs-dev
OverviewDiscussionsAdmin

save_watch

Watches: configure and unfurl free; saving is the paid step. Save a Watch to your key so you can recall it from any door and be told what changed since your last delivery. Saving is the paid step, at the published Watch rate per saved Watch per month (see list_standard_watches terms); with no free paid slot the answer is a plain payment-required with the next step, and nothing is saved or charged. Pass watchId to edit a Watch you saved: that is a new version and costs nothing more. 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. A standard Watch with no reading yet (its reading is not-yet-projected) is saved free, as pending coverage, and fills no paid slot; it becomes a paid Watch only if you choose. A domain Watch is saved free, as pending coverage, until a reading for it is published; a domain with no covered topic is refused with the reason and nothing is charged. Needs your key. Same content as POST /api/v1/watches.

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.
labelNoYour own name for the Watch.
domainNoYour domain in your own words, e.g. Arizona startup ecosystem. Use with topics instead of base.
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.
watchIdNoEdit this saved Watch (a new version) instead of saving a new one.
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

A4.1/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, leaving billing, auth and side-effect semantics entirely to the description — and it delivers: payment-required behavior with next step, that nothing is saved or charged on refusal, free pending-coverage slots, when a Watch becomes paid, and "Needs your key." This is far beyond what the structured fields convey.

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 scoping constraint is front-loaded, but the prose is a single dense block with repetition ("saving is the paid step" appears twice in back-to-back sentences) and several branching caveats that would read better as a short structured list. It is informative but not economically sized.

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 7-parameter, nested-object mutation with no output schema, the description covers billing, auth, edit semantics, coverage re-checking, refusal behavior and the free/paid slot lifecycle. Only the eventual return shape (Watch id, pending-coverage status) is left implicit, which is a minor gap given no output schema exists to carry it.

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 already 100%, so the baseline is 3, but the description adds real meaning the schema lacks: watchId is a new-version edit that costs nothing more, base and domain/topics are mutually exclusive paths, domain coverage is re-checked and only covered topics are kept, and coordinates keys are recorded but only depth and delivery are honoured today.

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 names a specific verb and resource ("Save a Watch to your key") and immediately frames the paid-versus-free distinction against the sibling operations unfurl_watch and configure. It does not explicitly name those siblings, so an agent must infer the boundary, which keeps this below a 5.

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 concrete when-to-use conditions: pass watchId to edit an existing Watch (a new version, no extra charge), start from a base standard Watch or supply domain+topics from get_quote, and it references list_standard_watches terms. What is missing is an explicit statement of when NOT to save (e.g. point the agent at unfurl_watch or list_saved_watches instead).

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