Zoning Signal

List Meetings

list_meetings

Read-onlyIdempotent

Return meeting readings across all cities, optionally filtered by date range or jurisdiction substring. Same response shape as meeting_index but with no required parameters — call with no args to get the full corpus, or pass a jurisdiction substring (e.g., "minneola") to filter by city without requiring an exact match. Use when you need to enumerate the full meeting record or scan across cities by date range.

Input Schema

TableJSON Schema

Name	Required	Description
`to_date`	No	Inclusive upper bound (ISO 8601 date). Omit for the latest reading.
`from_date`	No	Inclusive lower bound (ISO 8601 date). Omit to span back to the earliest reading.
`jurisdiction`	No	Optional case-insensitive substring to filter by city (e.g., "minneola"). Omit for all cities.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	No
`filters`	No
`meetings`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "type": "number"
+    },
+    "filters": {
+      "properties": {
+        "board": {
+          "type": "string"
+        },
+        "jurisdiction": {
+          "type": "string"
+        },
+        "year": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "meetings": {
+      "items": {
+        "properties": {
+          "board": {
+            "type": "string"
+          },
+          "document_type": {
+            "type": "string"
+          },
+          "jurisdiction": {
+            "type": "string"
+          },
+          "meeting_date": {
+            "type": "string"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          },
+          "voxel_lead": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

AddedMay 8, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds behavioral context by explaining that calling with no args returns the full corpus, jurisdiction filtering uses substring matching, and the response shape matches meeting_index. This goes beyond the annotations but doesn't describe pagination or output details, which are covered by the output schema.

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?

The description is two sentences, front-loaded with the core action, and every phrase adds value (purpose, alternatives, usage scenarios). No redundancy or fluff.

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 list tool with 3 optional params, an output schema, and strong annotations, the description covers the essential behavioral aspects, usage guidance, and relationship to siblings. It doesn't need to explain return values given the output schema, and the usage context is fully addressed.

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?

All three parameters have thorough descriptions in the schema (100% coverage), including examples and inclusive date semantics. The description primarily restates this information ('optionally filtered by date range or jurisdiction substring') and adds the usage pattern of no-args invocation. Since the schema does the heavy lifting, the description adds minimal new param meaning, so baseline 3 is appropriate.

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 clearly states the tool's purpose: 'Return meeting readings across all cities' and explicitly differentiates from sibling tool meeting_index by noting it has the same response shape but no required parameters. It also specifies its filtering capabilities (date range, jurisdiction substring), making it distinct from other list tools.

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?

The description provides explicit when-to-use guidance: 'Use when you need to enumerate the full meeting record or scan across cities by date range.' It also contrasts with meeting_index, implying when this tool is preferable (when no required parameters are needed). This meets the criterion of explicit usage context.

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

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