Skip to main content
Glama

Regrid

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Regrid Parcel By Point

regrid_parcel_by_point
Read-onlyIdempotent

Find parcels at a lat/lon point — returns the parcel(s) whose boundary contains or sits near the coordinate, with owner, zoning, land use, acreage, and boundary. Example: regrid_parcel_by_point({ lat: 38.8977, lon: -77.0365, _apiKey: "your-token" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latYesLatitude of the point, e.g. 38.8977
lonYesLongitude of the point, e.g. -77.0365
radiusNoOptional search radius in meters around the point
_apiKeyYesRegrid API token (get one free at regrid.com — 30-day sandbox)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-regrid-api-key",
+    "lat": 38.8977,
+    "lon": -77.0365
+  },
+  {
+    "_apiKey": "your-regrid-api-key",
+    "lat": 40.758,
+    "lon": -73.9855,
+    "radius": 500
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds that it returns parcels containing or 'near' the coordinate, clarifying the radius parameter's effect. No contradictions.

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

Conciseness5/5

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

Extremely concise: two sentences and a code example. Example is front-loaded and directly demonstrates usage. 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?

Covers purpose, parameters, and output fields. With no output schema, it would help to describe return format or typical fields. However, given simplicity and the example, it is mostly complete. Distinction from sibling could be clearer.

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 already describes all 4 parameters. Description adds value through two examples showing how to call with and without radius, clarifying that radius is for 'near' searches. This goes beyond the schema's text.

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?

Clearly states action (Find parcels), input (lat/lon point), and output (owner, zoning, land use, acreage, boundary). Distinguishes from sibling 'regrid_parcel_by_address' which uses an address instead of coordinates.

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

Usage Guidelines3/5

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

Provides an example but no explicit guidance on when to use this vs alternatives like 'regrid_parcel_by_address'. Does not mention when to include radius or any exclusions.

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

All Regrid toolsInspect
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