Skip to main content
Glama

lookup_tax_rate

Read-onlyIdempotent

Look up sales and use tax rates for a US or Canadian location. Provide a full street address for door-level accuracy, or a lat/lng pair for a geographic point lookup. Returns tax rates broken down by jurisdiction (state, county, city, district). Each call counts as one billable API call on the API key that makes it, the same as calling the Ziptax API directly. Within a task, reuse a result instead of repeating the same lookup. Requires a valid ZipTax API key sent in the X-API-KEY header or Authorization header. Get a key at https://platform.zip.tax

Input Schema

NameRequiredDescriptionDefault
latNoLatitude for coordinate-based lookup. Same door-level precision as an address
lngNoLongitude for coordinate-based lookup. Same door-level precision as an address
cityNoCity name
stateNoTwo-letter US state or Canadian province code (e.g., CA, ON)
countyNoCounty name
formatNoResponse format: 'json' (default) or 'xml'
addressNoFull street address for door-level geocoded lookup. Preferred input
adjustmentNoSet to 'auto' to enable state-specific unincorporated area adjustments
historicalNoHistorical period in YYYYMM format (e.g., 202601 for January 2026); lookback is limited to the past 12 months. Requires a Pro or Enterprise plan
postalcodeNoUS ZIP code (5-digit) or Canadian postal code. Least precise option: returns every rate overlapping the ZIP rather than one authoritative rate, with no adjustment for unincorporated areas. Use only when no address or lat/lng is available
country_codeNoCountry code: US (default) or CA for Canada. CA requires a Pro or Enterprise plan
sat_item_totalNoItem total for Tennessee Single Article Tax calculation
taxability_codeNoProduct taxability code (TIC) for product-specific tax rules. Requires a Pro or Enterprise plan

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds material context beyond them: each call is billable on the API key, results should be cached within a task, and a ZipTax API key is required in the X-API-KEY or Authorization header with a URL for obtaining one. Cost and auth prerequisites are exactly the kind of disclosure an agent cannot infer from structured fields.

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?

Five tight sentences, front-loaded with purpose then precision trade-offs, then cost, then auth. The billing and key-acquisition sentences are longer than strictly necessary for invocation, but both carry operationally relevant information rather than filler.

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?

For a 13-parameter, zero-required, no-output-schema lookup tool the description covers the essentials: input modes, return structure, cost model, and auth. It does not address fallback behavior when an address fails to geocode or what an error response looks like, which would round out the picture.

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%, so the schema already documents all 13 parameters, including the postalcode precision warning and the Pro/Enterprise gating on historical, country_code, and taxability_code. The description reinforces the address-versus-coordinates distinction and the jurisdiction breakdown but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 and resource ('Look up sales and use tax rates') plus the geographic scope (US or Canadian location) and the shape of the result (jurisdiction breakdown). An agent knows exactly what this returns without opening the schema, and the only sibling (get_account_metrics) is clearly unrelated.

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?

Gives concrete input-selection guidance: full street address for door-level accuracy versus lat/lng for a point lookup, and advises reusing results within a task rather than repeating identical lookups. It stops short of stating when not to use this tool or how it relates to any alternative lookup path, but the guidance present is actionable.

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.