Skip to main content
Glama

Close API

by city.close

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
NameRequiredDescriptionDefault
latNo
lonNo
modeNowalk, bike, or transit. Omit for all three.
pointsNoMany lat/lon points — one batch call.
block_geoidNo15-digit census block GEOID.
block_geoidsNoMany block GEOIDs — one batch call.

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: blocks_in_area provides per-block travel times, isochrone gives reachable areas, nearby_pois gives times to specific POIs, walkability_summary gives times to destination categories, and the rest handle place lookup, catalog, tokens, and authentication. No two tools overlap in functionality.

Naming Consistency2/5

Tool names mix styles: some start with verbs (find_place, get_catalog, redeem_code, request_sign_in), others are noun phrases (blocks_in_area, isochrone, nearby_pois, walkability_summary). There is no consistent verb_noun or noun pattern, making it harder for an agent to predict tool names.

Tool Count5/5

With 10 tools, the server covers core travel time analysis, place lookup, authentication, and membership. The count is well-scoped for the domain—neither too few to be useful nor too many to be confusing.

Completeness4/5

The tool surface covers the major workflows: finding places, getting base data, computing travel times in various forms (blocks, isochrones, POIs, summaries), and managing API keys. Minor gaps exist (e.g., no direct tool for single-point travel time to arbitrary coordinates), but the set is largely complete for the stated purpose.

Resources