Close API

nearby_pois

Nearby points of interest and the travel time to each, from a location (metered: 1 token per returned row). One origin: block_geoid or lat+lon; keep limit small to control spend and context size. Many origins (up to 250): block_geoids or points — one batch call and one rate-limit request, rows tagged by origin, no limit/pagination, so filter with type/mode/max_minutes. 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.

Input Schema

TableJSON Schema

Name	Required	Description
`lat`	No
`lon`	No
`mode`	No	walk, bike, or transit.
`type`	No	Destination type id (see get_catalog).
`limit`	No	Max rows (first page).
`points`	No	Many lat/lon points — one batch call.
`block_geoid`	No
`max_minutes`	No	Upper bound on travel time (<=30).
`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.5/5.0

Behavior5/5

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

No annotations provided; description fully shoulders transparency. Discloses token cost (1 per row), batch behavior (no limit/pagination, rows tagged by origin), truncation conditions (balance/row budget), and rate-limit request count. Contradicts nothing.

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?

Four sentences, each packed with information. Front-loaded with main action and key constraints. Could be slightly more structured (e.g., separate single vs batch), but no wasted words.

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?

9 parameters, no output schema, no annotations. Covers origins, batching, filtering, token cost, truncation. Lacks output format details but given complexity and zero annotations, the description is highly informative.

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 67%; description adds critical meaning: distinguishes single vs batch origins (lat+lon/block_geoid vs points/block_geoids), explains limit applies only to single origin, clarifies max_minutes cap (<=30). Does not detail every parameter but compensates with behavioral context.

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 verb ('travel time to each') and resource ('points of interest'), specifies origins (block_geoid or lat+lon) and batch capabilities, and distinguishes from siblings by highlighting batch processing and token costing.

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?

Provides explicit guidance: keep limit small for cost control, filter with type/mode/max_minutes, use batching to save requests. Does not explicitly state when not to use, but covers key usage scenarios.

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?