Skip to main content
Glama

Geocode address lists

geocode_addresses
Read-onlyIdempotent

Use this when the user wants to geocode addresses, convert addresses to latitude and longitude, or do a census tract lookup with a downloadable Excel and CSV file. US addresses only; up to 1,000 rows and 200,000 characters. Do not use for driving directions or addresses outside US coverage.

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": {
      "addresses": "<addresses>"
    },
    "name": "geocode_addresses"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressesYesUS addresses, one per line, or CSV with an Address or Street header; up to 200,000 characters. Example: 1437 Bannock St, Denver, CO 80202.

Output Schema

NameRequiredDescriptionDefault
countsYes
errorsYes
sourceYes
previewYes
downloadsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful behavioral context beyond annotations: US-only coverage, row and character limits, and output as downloadable Excel and CSV files. It does not cover rate limits or authentication, but the added context is substantial.

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 front-loaded with the primary use case, followed by constraints and exclusions. Every sentence earns its place by clarifying purpose, scope, limits, and what the tool should not be used for.

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 single-parameter read-only tool with rich annotations and an output schema, the description is complete enough. It covers purpose, usage conditions, exclusions, geographic scope, input limits, and output file format without redundant return-value explanation.

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 100%, so the baseline is 3. The description adds meaning by specifying a 1,000-row limit not present in the schema and by reinforcing the US-only address scope, which helps an agent understand the input constraints beyond the schema's 200,000-character limit.

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 states a clear verb and resource: geocode addresses, convert addresses to latitude/longitude, and perform census tract lookups. It is specific about scope, but it does not explicitly distinguish this tool from the sibling find_address_districts, especially since 'census tract lookup' could overlap with district lookup.

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

Usage Guidelines4/5

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

It gives explicit when-to-use guidance ('Use this when the user wants to geocode addresses...') and when-not-to-use guidance ('Do not use for driving directions or addresses outside US coverage'). It does not name the sibling tool or provide an explicit alternative for district lookup, so it falls short of a full 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources