Skip to main content
Glama

Zoning Signal

by com.zoningsignal
OverviewDiscussionsAdmin

List Watch Items

list_watch_items
Read-onlyIdempotent

Return The Watch, the field's forward calendar of pending events, scheduled hearings, regulatory sunsets, and condition-triggered milestones the observatory is tracking. Filter by status (pending / resolved / obsolete), horizon (imminent / near-term / structural), or scope (place / corridor / brief). Use to surface what the field is watching from any cognitive position.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
briefNoOptional: filter to items linked to a specific named-pattern brief.
placeNoOptional: filter to items scoped to a specific place dossier (e.g., "leesburg-florida").
statusNoFilter by lifecycle status. Defaults to 'pending' (active watch items only); pass 'all' for the full corpus including resolved + obsolete entries.
horizonNoOptional: filter to items in the named horizon band. Imminent = ≤14 days; near-term = ≤90 days; structural = >90 days or condition-triggered.
corridorNoOptional: filter to items scoped to a specific corridor (e.g., "us-27-south-lake").

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
statusNo
watch_itemsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "type": "number"
+    },
+    "status": {
+      "enum": [
+        "pending",
+        "resolved",
+        "obsolete",
+        "all"
+      ],
+      "type": "string"
+    },
+    "watch_items": {
+      "items": {
+        "properties": {
+          "outcome": {
+            "type": "object"
+          },
+          "scope": {
+            "type": "object"
+          },
+          "significance": {
+            "type": "object"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "subtitle": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "trigger_date": {
+            "type": "string"
+          },
+          "trigger_type": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "title",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds meaningful context by defining the content (pending events, hearings, sunsets, milestones) and the filter axes, which goes beyond what annotations state. No hidden behaviors are left undisclosed.

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

Conciseness5/5

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

Two tightly written sentences. The first states the resource and its contents; the second lists filters and the intended use. No wasted words, and the core purpose is front-loaded before the filter details.

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?

For a read-only listing tool with zero required parameters, a rich output schema, and fully documented parameters, the description is complete. It tells the agent what is returned, how to filter, and when to use it. Nothing critical is missing for correct invocation.

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 every parameter is already documented in the schema, including enum values and defaults. The description restates the filter categories (status, horizon, scope) but adds no new syntax or semantics beyond what the schema provides. Baseline 3 is appropriate because the schema carries the parameter documentation burden.

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 opens with a specific verb+resource ('Return The Watch') and immediately clarifies what that means: a forward calendar of pending events, hearings, sunsets, and milestones. It distinguishes itself from sibling list/describe tools by naming its unique subject (the observatory's watch items) and explicitly listing the filter dimensions.

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?

The closing line 'Use to surface what the field is watching from any cognitive position' gives a clear usage context. It does not explicitly contrast with alternatives like describe_watch or list_places, but the purpose is unambiguous enough that an agent can infer when this tool is appropriate versus others.

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