Zoning Signal

List Places

list_places

Read-onlyIdempotent

List every place dossier (per-jurisdiction reading) the observatory publishes. Optionally filter by state. Returns city, state, slug, signal strength, signal direction, and the dossier URL. Use to discover the available place-level coverage before calling describe_place. Phase 12 renamed it from list_cities to align with the canonical content-type vocabulary (the loader function is getAllContent("place"); URLs are /places/{slug}; the describe tool is describe_place).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`state`	No	Optional US state name (e.g., "Florida") to filter the result set. Omit for all places across all states.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`cities`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedAug 17, 2026
- removedOutput schema / properties / cities / items / properties / signal_direction
```
Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}
```
- removedOutput schema / properties / cities / items / properties / signal_strength
```
Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}
```

Changed1 schema field changedMay 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "cities": {
+      "items": {
+        "properties": {
+          "city": {
+            "type": "string"
+          },
+          "signal_direction": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "signal_strength": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "slug": {
+            "type": "string"
+          },
+          "state": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "city",
+          "state",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "count": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "cities",
+    "count"
+  ],
+  "type": "object"
+}

AddedMay 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description doesn't need to restate safety. It adds value by enumerating return fields (city, state, slug, signal strength, signal direction, dossier URL), which is behavioral context beyond the schema. No contradictions 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.

Conciseness3/5

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

The purpose is front-loaded, but the description includes dense implementation details (loader function getAllContent, URL patterns, rename history) that are not needed for invoking the tool. These extra sentences could be trimmed without losing value for the agent.

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?

With a simple single-param schema, output schema present (which covers return values), and the description summarizing return fields plus usage guidance, the definition is sufficiently complete for an agent to call the tool correctly. Minor gaps like pagination aren't relevant here.

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 coverage is 100% and the parameter description already covers filtering by state and omission semantics. The tool description repeats 'Optionally filter by state' without adding new constraints or nuance, so it adds no meaning 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 states 'List every place dossier' – a clear verb+resource – and distinguishes this tool from siblings like list_corridors/list_entities by the resource type 'place'. It also names the follow-up describe_place, making its role 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?

Explicitly says 'Use to discover the available place-level coverage before calling describe_place', giving a clear when-to-use. It does not explicitly exclude alternatives or compare to other list tools, but the context is sufficient for an agent to infer appropriate usage.

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?