mcp-livedatapro

validateAddressGeocode

Standardize messy street addresses, verify postal codes, and return rooftop GPS coordinates. Use when standardizing unformatted street addresses, verifying postal deliverability, and resolving rooftop GPS coordinates (lat/lon). Do not use for municipal land-use zoning laws (use getParcelZoningInfo) or IP address geolocation (use getIpIntelligence). Parses global postal databases and returns deliverable boolean plus standardized components.

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": {
      "raw_address": "<raw_address>"
    },
    "name": "validateAddressGeocode"
  }
}

Input Schema

Name	Required	Description	Default
`raw_address`	Yes	Unformatted, partial, or messy street address string including city/country.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 24, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / raw_address / examples
```
Added value: +[
+  "221B Baker St, Marylebone, London NW1 6XE, UK"
+]
```
- addedInput schema / properties / raw_address / maxLength
```
Added value: +300
```
- addedInput schema / properties / raw_address / minLength
```
Added value: +5
```

Changed1 schema field changedOct 24, 2026

changedInput schema / properties / raw_address / description

Previous value: -"Unformatted or partial street address string"New value: +"Unformatted, partial, or messy street address string including city/country."

First observedOct 21, 2026

TDQS

A4.2/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 usefully discloses the return contents (deliverable boolean plus standardized components) and the precision level (rooftop vs. coarse geocoding), but says nothing about cost, rate limits, authentication, or what happens when an address is undeliverable.

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?

Three sentences, front-loaded with the core capability followed by usage conditions and exclusions. Every sentence adds routing or scoping information; there is no filler.

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?

For a single-parameter lookup with no output schema and no annotations, the description covers purpose, alternatives, allowable input messiness, and roughly what comes back. A slightly fuller account of the response fields would make it complete, but an agent has what it needs to call it correctly.

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% and the schema description already specifies an unformatted, partial, or messy address string including city/country, with a worked example. The description's mention of 'messy' and 'partial' addresses restates rather than extends this, so the baseline 3 applies.

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 states three specific verbs and their resources: standardizing street addresses, verifying postal codes, and returning rooftop GPS coordinates. It explicitly names the sibling tools it is not (getParcelZoningInfo, getIpIntelligence), so an agent can distinguish it without opening any schema.

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 'use when' conditions (unformatted addresses, postal deliverability, rooftop coordinates) and explicit 'do not use for' exclusions that route to the correct alternative tools by name. Nothing is left to inference.

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?