Zoning Signal

Describe Pattern

describe_pattern

Read-onlyIdempotent

Return the full dossier for a named pattern: voxel_lead, signal_status (horizon/confidence), scope (spatial/temporal/topical/corridors), full exhibits inventory with detection metadata, defensive responses, provenance chain, related briefs, related places, related corridors, audiences, and the canonical surfaces (dossier URL, DefinedTerm @id, DefinedTermSet @id, atlas list URL). Use when an agent needs the structured pattern data to cite or analyze. Each pattern is a citable entity in the corpus's entity graph; the DefinedTerm canonical home gives AI agents a stable reference.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	The pattern slug (e.g., "self-storage-canary"). Use current_named_patterns to discover available slugs.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`name`	Yes
`slug`	Yes
`scope`	No
`claims`	Yes
`exhibits`	No
`named_at`	No
`surfaces`	No
`audiences`	No
`freshness`	Yes
`voxel_lead`	No
`signal_status`	No
`related_briefs`	No
`related_places`	No
`lifecycle_stage`	No
`provenance_chain`	No
`related_corridors`	No
`defensive_response`	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 changedAug 17, 2026

removedOutput schema / properties / signal_status / properties / confidence_pips
```
Removed value: -{
-  "maximum": 5,
-  "minimum": 0,
-  "type": "number"
-}
```

removedOutput schema / properties / signal_status / properties / direction

Removed value: -{
-  "enum": [
-    "rising",
-    "stable",
-    "cooling"
-  ],
-  "type": "string"
-}

removedOutput schema / properties / signal_status / properties / score

Removed value: -{
-  "maximum": 100,
-  "minimum": 0,
-  "type": "number"
-}

Changed1 schema field changedMay 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "audiences": {
+      "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"
+    },
+    "defensive_response": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "exhibits": {
+      "items": {
+        "properties": {
+          "date": {
+            "type": "string"
+          },
+          "detected_via": {
+            "type": "string"
+          },
+          "note": {
+            "type": "string"
+          },
+          "source": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "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"
+    },
+    "lifecycle_stage": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "named_at": {
+      "type": "string"
+    },
+    "provenance_chain": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "related_briefs": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "related_corridors": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "related_places": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "scope": {
+      "properties": {
+        "corridors": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "spatial": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "temporal": {
+          "type": "string"
+        },
+        "topical": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "signal_status": {
+      "properties": {
+        "confidence": {
+          "enum": [
+            "low",
+            "medium",
+            "high",
+            "very-high"
+          ],
+          "type": "string"
+        },
+        "confidence_pips": {
+          "maximum": 5,
+          "minimum": 0,
+          "type": "number"
+        },
+        "direction": {
+          "enum": [
+            "rising",
+            "stable",
+            "cooling"
+          ],
+          "type": "string"
+        },
+        "horizon": {
+          "type": "string"
+        },
+        "score": {
+          "maximum": 100,
+          "minimum": 0,
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "slug": {
+      "type": "string"
+    },
+    "surfaces": {
+      "properties": {
+        "defined_term_id": {
+          "type": "string"
+        },
+        "defined_term_set": {
+          "type": "string"
+        },
+        "dossier": {
+          "type": "string"
+        },
+        "list_in_atlas": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "url": {
+      "type": "string"
+    },
+    "voxel_lead": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "slug",
+    "name",
+    "url",
+    "claims",
+    "freshness"
+  ],
+  "type": "object"
+}

AddedMay 8, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare the tool read-only, idempotent, and non-destructive; the description adds useful context by specifying that it returns the full dossier and canonical stable references. No contradiction exists between the description and 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences front-load the return contract, then usage, then conceptual context. The long list of dossier contents is justified because it defines what 'full dossier' means and helps an agent decide whether to call this tool, though it is slightly verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with an output schema, the description covers purpose, contents, and stable-reference context well. A minor caveat is that the schema references 'current_named_patterns' while the sibling list includes list_patterns, which could slightly confuse slug discovery.

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?

The input schema covers the single slug parameter 100%, including an example and a pointer to discover available slugs. The description adds little beyond calling it a 'named pattern,' so the schema carries the semantic weight.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('Return the full dossier for a named pattern') and enumerates the dossier contents, making the tool's purpose clear. It is implicitly distinct from list_patterns as a detailed single-pattern lookup, but it does not explicitly name or compare against a sibling tool.

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 an explicit usage trigger: 'Use when an agent needs the structured pattern data to cite or analyze.' It does not provide exclusions or point to alternatives such as list_patterns for broader discovery, so it stops short of a 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?