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.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: the response shape matches meeting_index, jurisdiction filtering is a substring (not exact match), and calling with no args returns the full corpus. This goes beyond the annotations and helps the agent understand semantics.

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?

Three sentences with no fluff. The main purpose is front-loaded, then the optional filters, then a clear usage directive. Every sentence earns its place, and the sibling reference is included naturally.

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?

With an output schema present and annotations covering safety, the description covers all essential information: what it does, when to use it, how parameters behave, and how it differs from meeting_index. 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so each parameter is documented. The description adds extra meaning: clarifies that jurisdiction is a case-insensitive substring, and that omitting parameters yields the full corpus. It also implies date range filtering without exact match. This supplements the schema meaningfully.

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?

States a specific verb and resource: 'Return meeting readings across all cities'. It differentiates from sibling meeting_index by noting 'Same response shape as meeting_index but with no required parameters', so an agent can immediately see the distinction.

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?

Provides explicit usage guidance: 'Use when you need to enumerate the full meeting record or scan across cities by date range.' It also explains when to call with no args vs. with a jurisdiction substring, and implicitly contrasts with meeting_index by noting the required-parameter difference.

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?