Zoning Signal

Describe Place

describe_place

Read-onlyIdempotent

Return the dossier projection for a city, in the requested cognitive lens. Defaults to the synthesis projection (the multidimensional view that holds all lenses in superposition and names the dialectics). Pass a single-lens value to get the focused cognitive position. This is useful when the agent is acting on behalf of a user with a specific stake (developer underwriting, investor thesis, broker client argument, attorney precedent search, resident orientation, civic-leader regional coordination).

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/land-use-counsel/regulator → attorney; realtor/intermediary/real-estate-broker → broker; civic/government/official/governance → civic-leader; homeowner/citizen → resident; operator/site-selector/occupier → business; builder/land-developer → developer.	synthesis
`slug`	Yes	The place slug (e.g., "clermont-florida"). Use list_places 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."

Changed3 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 from a specific stakeholder position."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/land-use-counsel/regulator → attorney; realtor/intermediary/real-estate-broker → broker; civic/government/official/governance → civic-leader; homeowner/citizen → resident; operator/site-selector/occupier → business; builder/land-developer → 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"
+]

changedInput schema / properties / slug / description

Previous value: -"The place slug (e.g., \"clermont-florida\"). Use list_cities to discover available slugs."New value: +"The place slug (e.g., \"clermont-florida\"). Use list_places to discover available slugs."

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

First observedApr 29, 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, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds real behavioral value by explaining the default 'synthesis projection (the multidimensional view that holds all lenses in superposition and names the dialectics)' and the dispatch behavior when a single lens is passed. No contradiction with annotations.

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 sentences with the core action and default behavior front-loaded in the first sentence, followed by single-lens usage and stakeholder use-cases in the second. Every clause earns its place; no 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?

For a two-parameter tool with an output schema present and rich annotations, the description fully covers lens semantics, defaults, and when to use it. Return values need not be explained since an output schema exists. Nothing an agent needs to call this correctly is missing.

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. The description elevates this by explaining the meaning of the lens parameter (synthesis as the superposition of all lenses vs. a focused cognitive position) and mapping lenses to user stakes. The slug is already well documented in the schema with an example and pointer to list_places.

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 dossier projection for a city' — and introduces the tool's distinguishing feature, the cognitive lens that projects different viewpoints. Being place-scoped (vs. corridor/entity/meeting siblings) makes its purpose unambiguous.

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 enumerates concrete triggering contexts ('acting on behalf of a user with a specific stake: developer underwriting, investor thesis, broker client argument...'), telling an agent when this tool is the right call. It does not explicitly name sibling tools or state when not to use it, so exclusions are absent, though the provided context is strong.

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?