Zoning Signal

Describe Corridor

describe_corridor

Read-onlyIdempotent

Return the dossier projection for a corridor, in the requested cognitive lens. Same lens enum and default as describe_place. Corridor projections surface cross-municipal dialectics and shared-infrastructure dynamics that no single place dossier captures.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lens`	No	The cognitive position to project. Defaults to "synthesis". 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.	synthesis
`slug`	Yes	The corridor slug (e.g., "us-27-south-lake"). Use list_corridors 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`	No
`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: -"The cognitive position to project. Defaults to \"synthesis\". Single-lens values surface a focused projection."New value: +"The cognitive position to project. Defaults to \"synthesis\". 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."

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": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "slug": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "type": {
+      "enum": [
+        "corridor"
+      ],
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "slug",
+    "type",
+    "url",
+    "lens",
+    "projection",
+    "claims",
+    "freshness"
+  ],
+  "type": "object"
+}

First observedApr 29, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The annotations already establish that this is read-only and idempotent. The description adds meaningful behavioral context beyond that: the output is a lens-dependent projection, the lens behavior is shared with describe_place, and corridor projections have unique cross-municipal analytical scope.

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 filler. The core action is front-loaded, the lens behavior is clarified in the second sentence, and the distinguishing value of corridor projections is stated in the third without redundancy.

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 tool is simple, has an output schema, and its annotations cover safety and idempotency. The description provides sufficient differentiation from sibling tools and enough conceptual framing for an agent to call it 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?

Schema description coverage is 100%, and the schema already documents lens enums, defaults, aliases, and slug discovery via list_corridors. The description's mention of a 'cognitive lens' and 'same lens enum' adds conceptual flavor but not semantic detail 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 names a specific verb-resource pair: returning the dossier projection for a corridor in a chosen cognitive lens. It also differentiates this tool from its closest sibling by invoking describe_place and explaining that corridor projections capture cross-municipal dialectics that place dossiers cannot.

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 description gives clear contextual guidance by contrasting corridor-level projections with place-level dossiers and referencing describe_place's lens enum/default. It implies when a corridor should be used over a place, though it does not explicitly list exclusions or other alternatives.

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?