Close API

walkability_summary

Fastest travel time from a location to each destination category, by mode (metered: 1 token per returned row). One origin: block_geoid or lat+lon. Many origins (up to 250): block_geoids or points — one batch call and one rate-limit request, with rows tagged by origin. Batching saves requests and context, not tokens: it still charges per row. A non-empty truncated (+ truncated_reason) means the balance or row budget cut the batch short. A missing category means it is not reachable within 30 minutes.

Input Schema

TableJSON Schema

Name	Required	Description
`lat`	No
`lon`	No
`mode`	No	walk, bike, or transit. Omit for all three.
`points`	No	Many lat/lon points — one batch call.
`block_geoid`	No	15-digit census block GEOID.
`block_geoids`	No	Many block GEOIDs — one batch call.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJul 24, 2026

addedInput schema / properties / block_geoids

Added value: +{
+  "description": "Many block GEOIDs — one batch call.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / points

Added value: +{
+  "description": "Many lat/lon points — one batch call.",
+  "items": {
+    "properties": {
+      "lat": {
+        "type": "number"
+      },
+      "lon": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "lat",
+      "lon"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

First observedJul 22, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Discloses metering (1 token per row), batch behavior (rows tagged by origin), truncation signaling (non-empty truncated + truncated_reason), and the implication of missing categories (unreachable within 30 min). Since no annotations exist, the description fully carries the burden and does it well.

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?

The description is concise given the tool's complexity, with key information front-loaded. It could be slightly more structured (e.g., separating input and output behavior), but it remains clear and informative without unnecessary words.

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?

Covers input scenarios (single vs batch, origin types), behavioral details (metering, truncation, batching trade-offs), and output interpretation (missing categories). With no output schema, it adequately explains what to expect from results, making it contextually complete.

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 67% (lat/lon lack descriptions). The description adds value by explaining how parameters are used (single origin via lat+lon or block_geoid, batch via points or block_geoids, mode options). It compensates for schema gaps but does not enumerate each parameter.

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 clearly states the tool computes fastest travel times from an origin to destination categories by mode. It distinguishes itself from sibling tools like isochrone (which focuses on reachable areas) or nearby_pois (which lists points of interest).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly explains when to use single vs batch origins, mentions batching saves API requests and rate-limit requests but not tokens, and warns about truncated results. This provides clear guidance on tool selection and usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Close API 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?