EasyTerritory MCP

Geocode Addresses

geocode_address

Geocodes a list of customer addresses to coordinates with match confidence, without loading them as a point layer. Accepts address/address_line1/street, city, state, and postal columns (common CRM headers are mapped). accept_suboptimal_geocodes=true accepts ZIP-centroid matches. Cached addresses are free; billable lookups count against a monthly per-key quota, and past it the result is PROVIDER_QUOTA_EXCEEDED with limit, used, remaining, and period_resets_at. Returns geocoded_rows, which ingest_accounts can load. ingest_accounts also geocodes on its own.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`rows`	Yes
`use_cache`	No
`region_hint`	No
`country_hint`	No
`map_session_id`	No
`min_confidence`	No
`force_regeocode`	No
`accept_suboptimal_geocodes`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 9, 2026

removedInput schema / properties / guidance_handle

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Guidance Handle"
-}

First observedSep 29, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only mark readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false. The description adds critical behavior annotations do not: caching is free while billable lookups count against a monthly per-key quota, and the exact quota-exceeded response shape (PROVIDER_QUOTA_EXCEEDED with limit, used, remaining, period_resets_at). This is high-value behavioral context.

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 dense sentences covering purpose, input shape, quota behavior, and output/routing. Front-loads the core purpose but the quota sentence is long; still, every sentence earns its place with little waste.

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?

An output schema exists so return-value detail is not required; the description nonetheless names geocoded_rows and its downstream consumer. It covers cost/quota, input column mapping, and the sibling alternative. Completeness is slightly reduced by undocumented semantics of 6 of 8 parameters, though most are self-explanatory from names and defaults.

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 description coverage is 0%, so the description must compensate, and it does: it explains accepted address column variants (address/address_line1/street, city, state, postal) and mapping of common CRM headers, and explains accept_suboptimal_geocodes. It still omits the purpose of use_cache, region_hint, country_hint, map_session_id, min_confidence, and force_regeocode, leaving half of the 8 params opaque.

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?

States a specific verb (geocodes) plus resource (a list of customer addresses) and the output (coordinates with match confidence). The clause 'without loading them as a point layer' distinguishes it sharply from layer-building siblings like import_geojson or seed_build.

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?

The description names the alternative ingest_accounts twice: it says ingest_accounts also geocodes on its own, and that this tool's output can be loaded by ingest_accounts. It also clarifies when to relax matching (accept_suboptimal_geocodes=true for ZIP-centroid matches). This gives the agent a clear routing decision between the two geocoding paths.

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

All EasyTerritory MCP 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?