capabilities

Geocode a US street address (Census, TIGER interpolated)

location_us_geocode

Read-onlyIdempotent

Convert a one-line US street address into coordinates using the US Census Bureau Geocoder. Returns the standardised matched address, latitude and longitude to 6 decimal places, the TIGER/Line segment and parsed address components. Coordinates are interpolated along street address ranges, not rooftop or parcel positions. Use when: Convert this US street address to latitude and longitude. Not for: You need rooftop or parcel-level precision — Census coordinates are TIGER address-range interpolations. Related: location_us_geographies. Price: USD 0.003/call (x402), 0.002 (account key).

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of candidate matches to return, in the Census Bureau's own order. page.total always reports how many the Census Bureau returned in total, so a low limit never hides an ambiguous address.
`offset`	No	Zero-based index of the first candidate to return. The Census Bureau returns every match in one response, so paging is applied by Eckari over that set - pass page.next_offset to walk the remaining candidates without a second upstream lookup.
`address`	Yes	One-line US street address including city and state, e.g. "1600 Pennsylvania Ave NW, Washington, DC 20500".

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes	Capability output; full JSON Schema at https://api.eckari.com/v1/capabilities/location.us.geocode
`meta`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed9 schema fields changedAug 18, 2026

changedInput schema / properties / limit / description

Previous value: -"Maximum number of candidate matches to return, in the Census Bureau's own order. When the Census Bureau returns more than this, the extra candidates are omitted and has_more is true; total_candidates always reports how many it returned."New value: +"Maximum number of candidate matches to return, in the Census Bureau's own order. page.total always reports how many the Census Bureau returned in total, so a low limit never hides an ambiguous address."

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Zero-based index of the first candidate to return. The Census Bureau returns every match in one response, so paging is applied by Eckari over that set - pass page.next_offset to walk the remaining candidates without a second upstream lookup.",
+  "minimum": 0,
+  "type": "integer"
+}

removedOutput schema / properties / data / additionalProperties
```
Removed value: -false
```

addedOutput schema / properties / data / description

Added value: +"Capability output; full JSON Schema at https://api.eckari.com/v1/capabilities/location.us.geocode"

removedOutput schema / properties / data / properties

Removed value: -{
-  "attribution": {
-    "description": "Non-endorsement notice reproduced verbatim from the Census Bureau developer API terms of service (the published Census wording; the Geocoding Services API publishes no citation sentence of its own and the Census geocoding-services page points to these terms): \"This product uses the Census Bureau Data API but is not endorsed or certified by the Census Bureau.\" Display it wherever this result is shown or redistributed.",
-    "type": "string"
-  },
-  "benchmark": {
-    "description": "Census Bureau address-range benchmark used for the match (Public_AR_Current).",
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "candidates": {
-    "description": "Candidate matches in the Census Bureau's own order (best first), truncated to limit. Eckari applies no re-ranking.",
-    "items": {
-      "additionalProperties": false,
-      "properties": {
-        "address_components": {
-          "additionalProperties": false,
-          "description": "Parsed components of the matched address. Empty upstream values are returned as null.",
-          "properties": {
-            "city": {
-              "description": "City or place name as standardised by the Census Bureau.",
-              "type": [
-                "string",
-                "null"
-              ]
-            },
-            "from_address": {
-              "description": "Lowest house number of the matched TIGER address range.",
-              "type": [
-                "string",
-                "null"
-              ]
-            },
-            "pre_direction": {
-              "description": "Directional appearing before the street name (e.g. N, SW).",
-              "type": [
-                "string",
-                "null"
-              ]
-            },
-            "pre_type": {
-              "description": "Street type appearing before the name (e.g. AVENUE in \"Avenue of the Americas\").",
-              "type": [
-                "string",
-                "null"
-              ]
-            },
-            "state": {
-              "description": "Two-letter US state or territory code.",
-              "type": [
-                "string",
-                "null"
-              ]
-            },
-            "street_name": {
-              "description": "Street name without type or directional parts.",
-              "type": [
-                "string",
-                "null"
-              ]
-            },
-            "suffix_direction": {
-              "description": "Directional appearing after the street name (e.g. NW).",
-              "type": [
-                "string",
-                "null"
-              ]
-            },
-            "suffix_type": {
-              "description": "Street type appearing after the name (e.g. AVE, ST, BLVD).",
-              "type": [
-                "string",
-                "null"
-              ]
-            },
-            "to_address": {
-              "description": "Highest house number of the matched TIGER address range.",
-              "type": [
-                "string",
-                "null"
-              ]
-            },
-            "zip": {
-              "description": "Five-digit ZIP code recorded on the TIGER address range. This is Census reference data, not a USPS deliverability check.",
-              "type": [
-                "string",
-                "null"
-              ]
-            }
-          },
-          "required": [
-            "from_address",
-            "to_address",
-            "street_name",
-            "pre_type",
-            "pre_direction",
-            "suffix_type",
-            "suffix_direction",
-            "city",
-            "state",
-            "zip"
-          ],
-          "type": "object"
-        },
-        "lat": {
-          "description": "Latitude in decimal degrees (WGS 84), interpolated along the TIGER/Line street segment.",
-          "maximum": 90,
-          "minimum": -90,
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "lon": {
-          "description": "Longitude in decimal degrees (WGS 84), interpolated along the TIGER/Line street segment.",
-          "maximum": 180,
-          "minimum": -180,
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "matched_address": {
-          "description": "Standardised address as returned by the Census Bureau, upper-cased.",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "precision": {
-          "const": "tiger_interpolated",
-          "description": "Always tiger_interpolated: the coordinate is interpolated from the address range of a TIGER/Line street segment, not a rooftop, parcel centroid or surveyed point. Typical error is the length of a house-number range along one block.",
-          "type": "string"
-        },
-        "side": {
-          "description": "Side of the street segment the address falls on (L or R), as recorded in TIGER/Line.",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "tiger_line_id": {
-          "description": "Identifier of the TIGER/Line street segment the match was interpolated along.",
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "required": [
-        "matched_address",
-        "lat",
-        "lon",
-        "precision",
-        "tiger_line_id",
-        "side",
-        "address_components"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "has_more": {
-    "description": "True when total_candidates exceeds the number of candidates returned, so matches were omitted. Raise limit (up to 10) to see them.",
-    "type": "boolean"
-  },
-  "matched": {
-    "description": "True when the Census Bureau returned at least one candidate. False with an empty candidates array is a valid answer for an unrecognised or non-US address.",
-    "type": "boolean"
-  },
-  "query": {
-    "description": "The trimmed address as sent to the Census Bureau.",
-    "type": "string"
-  },
-  "total_candidates": {
-    "description": "Number of candidates the Census Bureau returned for this address, before limit was applied. A value above 1 means the address is ambiguous in TIGER/Line - typically the same house number on the same street in several ZIP codes - even when only one candidate is shown.",
-    "minimum": 0,
-    "type": "integer"
-  },
-  "vintage": {
-    "description": "Geography vintage echoed by the Census Bureau. The address-location endpoint does not return one, so this is null for this capability; see location.us.geographies.",
-    "type": [
-      "string",
-      "null"
-    ]
-  }
-}

removedOutput schema / properties / data / required

Removed value: -[
-  "query",
-  "matched",
-  "candidates",
-  "total_candidates",
-  "has_more",
-  "benchmark",
-  "vintage",
-  "attribution"
-]

addedOutput schema / properties / meta / properties / attribution_url
```
Added value: +{
+  "format": "uri",
+  "type": "string"
+}
```
addedOutput schema / properties / meta / properties / retrieved_at / format
```
Added value: +"date-time"
```

addedOutput schema / properties / meta / required

Added value: +[
+  "capability",
+  "version",
+  "retrieved_at",
+  "source",
+  "freshness",
+  "request_id"
+]

First observedAug 18, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds critical behavioral context: 'Coordinates are interpolated along street address ranges, not rooftop or parcel positions.' It also includes pricing information. No contradiction with annotations.

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?

The description is well-structured with a clear lead sentence, output details, precision caveat, usage guidance, related tool, and pricing. It is slightly long but every sentence adds value. Front-loaded with core purpose.

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?

Given the presence of an output schema (not shown here), the description does not need to detail return values. It covers purpose, precision limitations, usage guidance, pricing, and related tool. The paging behavior is documented in the schema parameter descriptions. The description is complete for an agent to make an informed decision.

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% with detailed parameter descriptions for limit, offset, and address. The description does not add additional semantics beyond what the schema provides, though it confirms the address format. Baseline score of 3 is appropriate.

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 clearly states the tool converts a one-line US street address into coordinates using the US Census Bureau Geocoder. It specifies the output includes latitude/longitude to 6 decimal places, TIGER/Line segment, and parsed address components. The related tool 'location_us_geographies' is mentioned, distinguishing it from a sibling.

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?

Explicitly provides 'Use when' and 'Not for' guidance, stating rooftop/parcel precision is not available. References the related tool 'location_us_geographies' as an alternative. This gives clear direction on when to use this tool versus alternatives.

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

All capabilities tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation4/5

Tools are largely distinct, targeting specific entities (UK company, US company, domain, LEI, FX, location, parcel, weather) or sub-aspects (e.g., accounts vs. charges vs. directors). Overlap exists between company.uk.profile and company.uk.status (both contain status info, but the latter is cheaper and focused). Also, company.uk.filings and company.us.filings_latest could be confused if an agent generalizes 'filings' across jurisdictions.

Naming Consistency5/5

All tools follow a consistent pattern: domain_entity_subject (e.g., company_uk_accounts, domain_expiry, weather_us_alerts). Underscores and lower case are used throughout. Verbs are implied by the noun (e.g., 'search' for lookup, 'detect' for identification). No mixed conventions or unpredictable names.

Tool Count4/5

24 tools is on the high side but still reasonable for a general-purpose data server spanning multiple domains (company, domain, entity, fx, location, parcel, weather). Each domain gets a cohesive set, and the documentation justifies each tool. Could be slightly leaner if some niche tools (e.g., domain_expiry vs. registration) were merged, but overall scoping is acceptable.

Completeness4/5

Each domain offers good coverage: UK company tools cover CRUD-like operations (profile, status, search, filings, charges, directors, owners, registered office); similarly for US companies (profile, filings, resolve, latest filings). Weather has forecast, observation, alerts. Parcel only detects carrier (no tracking). Missing features like advanced filtering on company filings or less common domains, but core workflows are covered.

Resources

Need Help?