Skip to main content
Glama

Zoning Signal

by com.zoningsignal
OverviewDiscussionsAdmin

Describe Watch

describe_watch
Read-onlyIdempotent

Return the full dossier for a watch item, the observatory's forward-looking observation primitive. Returns title, subtitle, scope (place / corridor / pattern / brief / region), trigger (type / date / condition), significance (horizon / confidence / why_it_matters_voxel), full body prose, four-clock freshness, and citation-stable claims[]. For RESOLVED watches, also returns the outcome cluster (outcome_type, outcome_summary, prediction_assessment with directional/horizon/significance assessments, lesson, citations), and the lesson surfaces as a stable claim_id (per the Phase 11 Citable Contract × Phase 8 Resolution Bridge compound). Use to ground citations in a specific watch's prediction or resolution; pair with list_watch_items for discovery.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesThe watch slug (e.g., "lake-bright-council-mar-23"). Use list_watch_items to discover available slugs.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
bodyNo
slugYes
typeYes
scopeNo
titleNo
claimsYes
outcomeYes
triggerNo
subtitleNo
freshnessYes
significanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedOutput schema / properties / claims / items / properties / id / description
      Previous value: -"Full claim_id slug — `{scope}.{facet}.{noun}`."New value: +"Full claim_id slug, in the form `{scope}.{facet}.{noun}`."
    • changedOutput schema / properties / freshness / properties / corpus_last_harvested / description
      Previous value: -"YYYY-MM-DD — most recent harvest_date in corpus."New value: +"YYYY-MM-DD: most recent harvest_date in corpus."
    • changedOutput schema / properties / freshness / properties / dossier_last_material_update / description
      Previous value: -"YYYY-MM-DD — when this dossier last changed."New value: +"YYYY-MM-DD: when this dossier last changed."
    • changedOutput schema / properties / freshness / properties / page_last_rendered / description
      Previous value: -"ISO 8601 — request-time stamp."New value: +"ISO 8601: request-time stamp."
  2. Changed1 schema field changed
    • removedOutput schema / properties / significance / properties / confidence_pips
      Removed value: -{
-  "type": "number"
-}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "body": {
+      "type": "string"
+    },
+    "claims": {
+      "items": {
+        "properties": {
+          "citations": {
+            "items": {
+              "properties": {
+                "id": {
+                  "type": "string"
+                },
+                "url": {
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "facet": {
+            "description": "Structural facet category.",
+            "enum": [
+              "primary_force",
+              "voxel_lead",
+              "exhibit",
+              "defensive_response",
+              "lesson",
+              "notable_decision",
+              "voting_record"
+            ],
+            "type": "string"
+          },
+          "id": {
+            "description": "Full claim_id slug — `{scope}.{facet}.{noun}`.",
+            "type": "string"
+          },
+          "schema_id": {
+            "description": "Full @id URL for JSON-LD reference.",
+            "type": "string"
+          },
+          "text": {
+            "description": "Claim text, verbatim.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "facet",
+          "text",
+          "schema_id",
+          "citations"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "freshness": {
+      "properties": {
+        "corpus_last_harvested": {
+          "description": "YYYY-MM-DD — most recent harvest_date in corpus.",
+          "type": "string"
+        },
+        "dossier_last_material_update": {
+          "description": "YYYY-MM-DD — when this dossier last changed.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "page_last_rendered": {
+          "description": "ISO 8601 — request-time stamp.",
+          "type": "string"
+        },
+        "site_build_committed": {
+          "description": "Short git SHA.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "corpus_last_harvested",
+        "page_last_rendered",
+        "site_build_committed"
+      ],
+      "type": "object"
+    },
+    "outcome": {
+      "properties": {
+        "citations": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "lesson": {
+          "type": "string"
+        },
+        "outcome_summary": {
+          "type": "string"
+        },
+        "outcome_type": {
+          "type": "string"
+        },
+        "prediction_assessment": {
+          "type": "object"
+        },
+        "resolved_at_meeting": {
+          "type": "string"
+        },
+        "resolved_date": {
+          "type": "string"
+        },
+        "status": {
+          "enum": [
+            "pending",
+            "resolved",
+            "obsolete"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "status"
+      ],
+      "type": "object"
+    },
+    "scope": {
+      "properties": {
+        "brief": {
+          "type": "string"
+        },
+        "corridor": {
+          "type": "string"
+        },
+        "pattern": {
+          "type": "string"
+        },
+        "place": {
+          "type": "string"
+        },
+        "region": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "significance": {
+      "properties": {
+        "confidence": {
+          "type": "string"
+        },
+        "confidence_pips": {
+          "type": "number"
+        },
+        "horizon": {
+          "type": "string"
+        },
+        "score": {
+          "type": "number"
+        },
+        "why_it_matters_voxel": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "slug": {
+      "type": "string"
+    },
+    "subtitle": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "trigger": {
+      "properties": {
+        "condition": {
+          "type": "string"
+        },
+        "date": {
+          "type": "string"
+        },
+        "type": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "type": {
+      "enum": [
+        "watch"
+      ],
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "slug",
+    "type",
+    "url",
+    "outcome",
+    "claims",
+    "freshness"
+  ],
+  "type": "object"
+}
  4. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds behavioral nuance by detailing the special handling of RESOLVED watches (outcome cluster, lesson surfacing as claim_id) and the compound contract reference. This goes beyond annotations, though it does not discuss side effects or auth, which are already covered.

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?

The description is a single dense paragraph that front-loads the purpose and then lists return fields, resolved handling, and usage. It is comprehensive but slightly verbose with technical jargon (e.g., 'Phase 11 Citable Contract × Phase 8 Resolution Bridge compound'). No redundant sentences, but could be tighter.

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?

Given the tool's complexity and the presence of an output schema, the description goes beyond what is required by explaining the return structure, the resolved-watch special case, and the citation-grounding use case. It also names the companion discovery tool. An agent has all necessary context to call this tool correctly.

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?

The schema covers the single parameter (slug) fully with an example and discovery instruction. The description does not add new semantic detail about the parameter itself; it merely reinforces the discovery method already in the schema. Baseline of 3 applies due to 100% schema coverage.

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?

The description states a specific verb and resource: 'Return the full dossier for a watch item'. It clearly identifies the resource (watch) and the action (return dossier), and differentiates from siblings by mentioning list_watch_items for discovery. The purpose is unambiguous and distinct.

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

Usage Guidelines5/5

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

It explicitly states when to use this tool: 'Use to ground citations in a specific watch's prediction or resolution' and pairs it with list_watch_items for discovery. This gives a clear use case and directs to the alternative for finding watches, leaving no ambiguity about selection.

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

All Zoning Signal 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