Skip to main content
Glama

Regrid

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Regrid Parcel By Address

regrid_parcel_by_address
Read-onlyIdempotent

Look up the parcel — owner, zoning, land use, boundaries — for an address. Searches Regrid's nationwide US/CA parcel database by full address string and returns parcel number, owner, mailing address, land use, zoning, acreage, and location. Example: regrid_parcel_by_address({ query: "1600 Pennsylvania Ave NW, Washington, DC", _apiKey: "your-token" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax parcels to return (default 5, max 20)
queryYesFull address string, e.g. "1600 Pennsylvania Ave NW, Washington, DC 20500"
_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",
+    "query": "1600 Pennsylvania Ave NW, Washington, DC 20500"
+  },
+  {
+    "_apiKey": "your-regrid-api-key",
+    "limit": 10,
+    "query": "350 Fifth Avenue, New York, NY 10118"
+  }
+]
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds value by detailing the output fields (parcel number, owner, land use, etc.) and specifying the database scope (US/CA). This provides behavioral context beyond what annotations offer, though it doesn't cover edge cases like pagination or error handling.

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?

The description is concise with only two sentences and an inline code example. Every sentence is informative, and the example demonstrates usage. No unnecessary words or repetition.

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?

Given the tool's simplicity (3 params, no output schema, rich annotations), the description adequately covers what the tool does and what it returns. It specifies the geographic scope and includes an example. However, it could be slightly improved by mentioning the default limit or error handling, but overall satisfactory.

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%, with all three parameters described. The description provides an example with typical values but does not add new semantics beyond what the schema already provides. The example is helpful but doesn't elevate the score above baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool looks up parcel information for a given address, specifying the verb 'look up' and the resource 'parcel.' It lists the types of data returned (owner, zoning, etc.), making the purpose clear. However, it does not explicitly distinguish itself from the sibling tool 'regrid_parcel_by_point,' which uses coordinates instead of addresses.

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

Usage Guidelines2/5

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

The description implies the tool is used when you have an address and want parcel data, but it provides no guidance on when not to use it or when to use alternatives like regrid_parcel_by_point. No explicit context for tool selection is given.

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