Skip to main content
Glama

acuris-mcp

by com.acuris-geo

enrich_us_ca_address

Address → census & geographic codes (USA + Canada), FREE with validation.

USA: state & county FIPS, census tract (11-digit GEOID), block group,
CBSA/MSA, congressional district (119th Congress), school district.
Canada: province, census division, dissemination area, census subdivision,
census tract, CMA/CA, federal electoral district. Sources: US Census
Bureau TIGER/Line; Statistics Canada (open data).

The enrichment is attached when the address resolves to a house-number- or
street-accurate match; centroid-only matches return no enrichment (the
point could fall in the wrong area). `country` must be "usa" or "can".

Cost: 1 validation credit (the enrichment itself is free); failed lookups
are refunded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNo
stateNo
streetNo
countryYes
postcodeNo
address_lineNo
house_numberNo

TDQS

A4.2/5.0
Behavior5/5

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

With no annotations, the description discloses key behavioral traits: enrichment only on accurate matches, not centroid; cost structure of 1 validation credit with refund on failure. This is comprehensive for a tool with no annotations.

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 well-structured with a brief overview, a bullet-like list of codes for each country, and separate paragraphs for match requirements and cost. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 7 parameters, no output schema, and no annotations, the description covers purpose, constraints, and cost but lacks parameter descriptions and output format details. It mentions enrichment is attached but doesn't describe the return structure, which is needed since no output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description only mentions that country must be 'usa' or 'can'. Other parameters (city, state, street, postcode, address_line, house_number) are listed in schema but not described in the description. The description implies address_line or street+house_number are needed for accurate matches, but doesn't clarify their roles or formatting.

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 that the tool enriches an address with census and geographic codes for USA and Canada, listing specific codes for each country. It differentiates from sibling tools like geocode_address by specifying it returns census/geographic codes, not just coordinates.

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?

The description provides clear context: enrichment is only for USA and Canada, requires house-number- or street-accurate match, and country must be 'usa' or 'can'. It doesn't explicitly compare to siblings or state when not to use, but the purpose is distinct enough.

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

All acuris-mcp toolsInspect
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

Most tools target distinct operations: validation (single/batch), geocoding, reverse geocoding, enrichment, UK postcode expansion, and account management. The main overlap is between enrich_us_ca_address and validate_address, which also includes an enrichment block for US/CA matches, potentially causing confusion about which to use.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (e.g., check_balance, expand_uk_postcode, validate_addresses_batch). The naming is uniform and predictable across the set.

Tool Count5/5

8 tools is well within the ideal 3-15 range and appropriately scoped for a geocoding/validation API. Each tool serves a distinct function without unnecessary bloat, and the count reflects the complexity of the domain.

Completeness4/5

The core workflows—single and batch validation, forward and reverse geocoding, enrichment, and UK postcode expansion—are covered. Minor gaps include the lack of a batch geocoding tool and the redundant enrichment functionality already present in validate_address, but these do not create dead ends.

Resources