Skip to main content
Glama
Sign In

mcp-server

by com.interzoid
OverviewDiscussionsAdmin

interzoid_sales_use_tax_rates

Read-onlyIdempotent

Current US sales and use tax rates for any address, ZIP code, city, or state, broken down into state, county, city, and special district rates plus the combined rate. A full street address gives the most accurate rate. For e-commerce checkout, invoicing, tax compliance, and accounting. Cost: $0.25 USDC via x402.

Input Schema

NameRequiredDescriptionDefault
lookupYesFull street address, ZIP code, city, or state
languageNoOptional. Two-letter code for results in that language (default English): fr, de, it, es, ja, pt, zh, ar, nl, el, tr, ko, sv, vi, th, id. Same price in every language.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
+  "description": "Optional. Two-letter code for results in that language (default English): fr, de, it, es, ja, pt, zh, ar, nl, el, tr, ko, sv, vi, th, id. Same price in every language.",
+  "enum": [
+    "fr",
+    "de",
+    "it",
+    "es",
+    "ja",
+    "pt",
+    "zh",
+    "ar",
+    "nl",
+    "el",
+    "tr",
+    "ko",
+    "sv",
+    "vi",
+    "th",
+    "id"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / lookup / examples
      Added value: +[
+  "Beverly Hills, CA 90210"
+]
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior. The description adds the non-obvious economics — $0.25 USDC via x402 payment — and the shape of the returned rate breakdown, which the agent could not 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences, front-loaded with what the tool returns, then the accuracy caveat, then use cases and price. No filler or repetition of schema content.

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?

With no output schema, the description correctly supplies the return structure (per-jurisdiction plus combined rate), and it covers the payment requirement and best-practice input. An agent has everything needed to decide and call correctly.

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 coverage is 100%, so the baseline is 3, but the description adds decision-relevant meaning: the lookup parameter accepts anything from a state down to a full street address, and precision of the input drives accuracy of the rate. The language parameter is not addressed here, but the schema fully documents it.

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?

Names a specific resource (current US sales and use tax rates) and the exact input surface (address, ZIP, city, or state), plus the granularity of the result (state, county, city, special district, combined). This clearly separates it from sibling rate tools like interzoid_eu_vat_rates and interzoid_customs_duty_rates.

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 explicit application contexts (e-commerce checkout, invoicing, tax compliance, accounting) and an accuracy rule: a full street address yields the most accurate rate. It stops short of naming when to use a sibling instead (e.g. EU VAT lookups), so no exclusion guidance.

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

All mcp-server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources