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

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?