Zoning Signal

Describe Meeting

describe_meeting

Read-onlyIdempotent

Return the full dossier projection for a meeting reading, in the requested cognitive lens. Same lens enum and default as describe_place / describe_corridor: eight total projections (seven stakeholder lenses, namely developer, investor, broker, attorney, business, resident and civic-leader, plus synthesis as the default). Returns the lens-projected body, full frontmatter (jurisdiction, board, meeting_date, document_type, key_signals, vote tallies), citation-stable claims[] (per the Phase 11 Citable Contract; populates as meeting claim scopes graduate), four-clock freshness, and the structured record_status block (record_type / meeting_status / outcome_status / minutes_available / vote_final). The last prevents agents from summarizing agenda intent as completed action. Use to ground citations in a specific meeting's reading; pair with list_meetings or meeting_index for discovery.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lens`	No	Optional cognitive lens. Default: synthesis (the whole-picture multi-projection view). Canonical lenses: developer, investor, broker, attorney, business, resident, civic-leader. Aliases route to canonical (legal/lawyer/counsel/regulator → attorney; realtor/intermediary → broker; civic/government → civic-leader; homeowner → resident; operator/site-selector → business; builder → developer). When the requested lens is not present in the dossier body, the response falls back to synthesis with fell_back_to_synthesis: true.
`slug`	Yes	The meeting slug (e.g., "leesburg-pc-2026-01"). Use list_meetings or meeting_index to discover available slugs.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`lens`	Yes
`slug`	Yes
`type`	Yes
`title`	No
`claims`	Yes
`freshness`	Yes
`projection`	Yes
`frontmatter`	No
`record_status`	Yes
`available_lenses`	No
`lens_was_requested`	No
`fell_back_to_synthesis`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 27, 2026

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."

Changed2 schema fields changedMay 10, 2026

changedInput schema / properties / lens / description

Previous value: -"Optional cognitive lens. Default: synthesis (the whole-picture multi-projection view). Seven stakeholder lenses available: developer, investor, resident, business, civic, infrastructure, policy. When the requested lens is not present in the dossier body, the response falls back to synthesis with fell_back_to_synthesis: true."New value: +"Optional cognitive lens. Default: synthesis (the whole-picture multi-projection view). Canonical lenses: developer, investor, broker, attorney, business, resident, civic-leader. Aliases route to canonical (legal/lawyer/counsel/regulator → attorney; realtor/intermediary → broker; civic/government → civic-leader; homeowner → resident; operator/site-selector → business; builder → developer). When the requested lens is not present in the dossier body, the response falls back to synthesis with fell_back_to_synthesis: true."

changedInput schema / properties / lens / enum

Previous value: -[
-  "synthesis",
-  "developer",
-  "investor",
-  "resident",
-  "business",
-  "civic",
-  "infrastructure",
-  "policy"
-]New value: +[
+  "synthesis",
+  "developer",
+  "investor",
+  "broker",
+  "attorney",
+  "business",
+  "resident",
+  "civic-leader"
+]

Changed1 schema field changedMay 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "available_lenses": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "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"
+    },
+    "fell_back_to_synthesis": {
+      "type": "boolean"
+    },
+    "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"
+    },
+    "frontmatter": {
+      "type": "object"
+    },
+    "lens": {
+      "type": "string"
+    },
+    "lens_was_requested": {
+      "type": "string"
+    },
+    "projection": {
+      "type": "string"
+    },
+    "record_status": {
+      "properties": {
+        "meeting_status": {
+          "enum": [
+            "scheduled",
+            "convened",
+            "cancelled"
+          ],
+          "type": "string"
+        },
+        "minutes_available": {
+          "type": "boolean"
+        },
+        "outcome_status": {
+          "enum": [
+            "pending",
+            "recorded"
+          ],
+          "type": "string"
+        },
+        "record_type": {
+          "enum": [
+            "agenda",
+            "minutes"
+          ],
+          "type": "string"
+        },
+        "vote_final": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "record_type",
+        "meeting_status",
+        "outcome_status",
+        "minutes_available",
+        "vote_final"
+      ],
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "slug": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "type": {
+      "enum": [
+        "meeting"
+      ],
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "slug",
+    "type",
+    "url",
+    "lens",
+    "projection",
+    "claims",
+    "freshness",
+    "record_status"
+  ],
+  "type": "object"
+}

AddedMay 9, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description details the returned blocks (lens-projected body, frontmatter, claims[], freshness, record_status) and, crucially, explains that record_status prevents agents from treating agenda intent as completed action. This is exactly the kind of behavioral context that helps an agent use results correctly.

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?

Although longer than a minimal description, every sentence carries information: the first sentence states the core action, subsequent sentences enumerate outputs and end with a practical warning and usage direction. It is front-loaded and free of filler.

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?

The combination of annotations, a 100%-covered schema, an output schema, and this description gives an agent everything needed to select and call the tool: what it returns, when to use it, how to discover slugs, and the shared lens semantics with siblings. No material gap remains.

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 the baseline is 3, but the description adds value by naming the seven stakeholder lenses and stating the lens enum/default is the same as describe_place/describe_corridor. It also reinforces slug discovery with list_meetings/meeting_index, going slightly beyond the schema.

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 and resource: 'Return the full dossier projection for a meeting reading' and later says 'Use to ground citations in a specific meeting's reading.' This clearly differentiates describe_meeting from siblings like describe_place/describe_corridor by the meeting resource.

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 a clear use case ('Use to ground citations in a specific meeting's reading') and points to list_meetings/meeting_index for discovery, plus notes the lens enum is shared with describe_place/describe_corridor. It stops short of explicitly saying when not to use sibling describe tools, so it is not a full 5.

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?