Zoning Signal

List Patterns

list_patterns

Read-onlyIdempotent

List every named pattern in the Pattern Atlas. A named pattern is a coined recurring structure observed across multiple jurisdictions or multiple meetings (e.g., "The Quiet Revolution"). Returns slug, display name, canonical pattern URL (/patterns/{slug}, the DefinedTerm canonical home as of Phase 9), lifecycle stage, horizon, confidence, exhibits count, spatial scope, related briefs, and the voxel_lead. Use as the discovery surface for the Pattern Atlas; pair with describe_pattern for full dossier detail. Phase 12 renamed it from current_named_patterns to align with the canonical content-type vocabulary (loader: getAllContent("pattern"); URLs: /patterns/{slug}; describe tool: describe_pattern).

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	No
`patterns`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedAug 17, 2026
- addedOutput schema / properties / patterns / items / properties / confidence
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / patterns / items / properties / direction
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / patterns / items / properties / horizon
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / patterns / items / properties / signal_score
```
Removed value: -{
-  "type": "number"
-}
```

Changed1 schema field changedMay 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "type": "number"
+    },
+    "patterns": {
+      "items": {
+        "properties": {
+          "audiences": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "canonical_url": {
+            "type": "string"
+          },
+          "direction": {
+            "type": "string"
+          },
+          "exhibits_count": {
+            "type": "number"
+          },
+          "lifecycle_stage": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "pattern_url": {
+            "type": "string"
+          },
+          "related_briefs": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "signal_score": {
+            "type": "number"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "spatial": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "voxel_lead": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "name",
+          "pattern_url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

AddedMay 9, 2026

TDQS

A4.3/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. The description adds meaningful context by stating the tool returns 'every named pattern,' enumerating the returned fields, and explaining the canonical pattern URL. It does not mention pagination or freshness, but the output schema and strong annotation coverage reduce the burden.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Purpose and usage are front-loaded and clear, but the description includes verbose historical and implementation details such as 'Phase 12 renamed it,' 'Phase 9 DefinedTerm canonical home,' and 'loader: getAllContent("pattern").' These add context but are not essential for an agent to call the tool, and the URL pattern is repeated.

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 zero-parameter, read-only list tool with an output schema and rich annotations, the description covers purpose, scope, return fields, canonical URL convention, and sibling relationship. Nothing essential for correct invocation 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?

The tool has zero parameters, so the baseline is 4. The description still adds semantic value by defining what a 'named pattern' is and what fields will be returned, which helps an agent interpret results even without an input schema to document.

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 states a specific verb and resource: 'List every named pattern in the Pattern Atlas.' It defines 'named pattern' concretely with an example and names the sibling describe_pattern, so an agent can distinguish this discovery tool from detail-lookup tools and other list_* siblings without opening schemas.

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 explicitly says 'Use as the discovery surface for the Pattern Atlas; pair with describe_pattern for full dossier detail.' This gives clear when-to-use guidance and points to the alternative for deeper detail. It does not explicitly contrast with semantic_search or other list tools, but for a list-all discovery tool the guidance 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?