Zoning Signal

Describe Zoning Signal

describe_zoning_signal

Read-onlyIdempotent

Return the canonical product description for Zoning Signal — what the observatory is, the four artifact types it publishes, the regional scope of current coverage, and the methodology. Call once per session to ground subsequent tool calls in canonical context.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`built_by`	No
`surfaces`	Yes
`description`	Yes
`methodology`	Yes
`artifact_types`	Yes
`regional_scope`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "artifact_types": {
+      "items": {
+        "properties": {
+          "purpose": {
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          },
+          "url_pattern": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "type",
+          "url_pattern",
+          "purpose"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "built_by": {
+      "properties": {
+        "studio": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "description": {
+      "type": "string"
+    },
+    "methodology": {
+      "properties": {
+        "cognitive_lenses": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "default_projection": {
+          "type": "string"
+        },
+        "summary": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "name": {
+      "type": "string"
+    },
+    "regional_scope": {
+      "properties": {
+        "cities": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "primary_region": {
+          "type": "string"
+        },
+        "state": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "surfaces": {
+      "properties": {
+        "decoder_index": {
+          "type": "string"
+        },
+        "llms_full": {
+          "type": "string"
+        },
+        "llms_index": {
+          "type": "string"
+        },
+        "mcp_endpoint": {
+          "type": "string"
+        },
+        "mcp_manifest": {
+          "type": "string"
+        },
+        "patterns_atlas": {
+          "type": "string"
+        },
+        "schema_url": {
+          "type": "string"
+        },
+        "site": {
+          "type": "string"
+        },
+        "sitemap": {
+          "type": "string"
+        },
+        "status_url": {
+          "type": "string"
+        },
+        "track_record": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "site",
+        "mcp_endpoint",
+        "status_url",
+        "schema_url"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "name",
+    "description",
+    "artifact_types",
+    "methodology",
+    "surfaces"
+  ],
+  "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, and the description is consistent with those. It adds value by specifying what the canonical description contains and by recommending session-level caching behavior ('once per session'), which is not in the 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?

Single sentence front-loads the verb and resource, then enumerates the covered content in a compact clause. No filler or repetition; every phrase earns its place.

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 zero parameters, an output schema present, and annotations covering safety, the description fully explains the tool's role and session-level usage. It is complete for the tool's simplicity and context.

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?

Tool accepts zero parameters, so the schema needs no elaboration. Baseline for zero params is 4; the description adds no contradictory or redundant parameter info.

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?

Description opens with a specific action ('Return the canonical product description') and names the exact resource (Zoning Signal), then spells out the content domains (observatory, artifact types, regional scope, methodology). This distinguishes it from sibling describe_* tools, which target different entities.

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?

Explicitly states 'Call once per session to ground subsequent tool calls in canonical context,' providing clear when-to-use advice. It does not mention when not to use it or name alternatives, so it stops short of 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?