mcp-livedatapro

getParcelZoningInfo

Municipal land use zoning codes, parcel boundaries, max building height/FAR, and permitted commercial uses. Use when inspecting municipal land-use zoning codes (e.g., R-2, C-3, Mixed-Use), parcel lot size, maximum building height/FAR, flood risk, and short-term Airbnb legality for a specific street address or GPS coordinate. Do not use for simple address formatting (use validateAddressGeocode) or home price averages (use getRealEstateStats).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address_or_coordinates": "<address_or_coordinates>"
    },
    "name": "getParcelZoningInfo"
  }
}

Input Schema

Name	Required	Description	Default
`address_or_coordinates`	Yes	Full street address or comma-separated GPS coordinates (lat,lon) of the land parcel.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 24, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / address_or_coordinates / examples
```
Added value: +[
+  "350 Fifth Ave, New York, NY 10118"
+]
```
- addedInput schema / properties / address_or_coordinates / minLength
```
Added value: +5
```

Changed1 schema field changedOct 24, 2026

changedInput schema / properties / address_or_coordinates / description

Previous value: -"Street address or GPS coordinates (lat,lon)"New value: +"Full street address or comma-separated GPS coordinates (lat,lon) of the land parcel."

First observedOct 21, 2026

TDQS

A4.3/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It implies a read-only inspection use case and enumerates returned data categories, but it does not explicitly state read-only/no-side-effect behavior, authentication/rate-limit expectations, or response structure.

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 compact and front-loaded: it leads with the data domain, then states the use case and exclusions. Every sentence contributes directly to selection or invocation, with no filler.

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?

For a simple one-parameter lookup with no output schema, the description is sufficiently complete: it lists the key data categories returned and provides clear routing against siblings. Missing formal response shape is minor given the enumerated output categories and low schema complexity.

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 description coverage is 100% for the single parameter, so the schema already explains address or comma-separated GPS coordinates with an example. The description mentions the same address-or-coordinate input but adds no syntax or format details beyond the schema, making 3 the appropriate baseline.

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 names the specific resource: municipal land-use zoning codes, parcel boundaries, max building height/FAR, permitted commercial uses, flood risk, and Airbnb legality. The phrasing 'Use when inspecting...' makes the action clear, and the named alternatives distinguish it from address validation and real-estate pricing tools.

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?

It gives explicit when-to-use guidance with concrete examples (R-2, C-3, Mixed-Use) and explicitly says when not to use it, routing agents to validateAddressGeocode for address formatting and getRealEstateStats for home price averages.

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

All mcp-livedatapro 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?