Skip to main content
Glama

Bullion Trading: Gold & Silver

Estimate sales tax

estimate_sales_tax
Read-onlyIdempotent

Whether a US state charges sales tax on bullion, the threshold if any, and an estimate for an order amount. Estimate only; the final tax is shown at checkout. Includes the state page link. Use when the user asks about US sales tax on a bullion purchase. Read-only; not tax advice.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "state": "<state>"
    },
    "name": "estimate_sales_tax"
  }
}

Input Schema

NameRequiredDescriptionDefault
formNoProduct form; some states tax coins and bars differently
metalNogold, silver, platinum or palladium
stateYesUS state: 2-letter code (NY) or name (New York)
amountNoOrder amount in USD

Output Schema

NameRequiredDescriptionDefault
notesYes
stateYes
taxableYes
warningsYes
rule_textYes
disclaimerYes
price_timeYes
source_urlYes
estimate_taxYes
threshold_usdYes
can_checkout_onlineYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / can_checkout_online
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / warnings
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "source_url",
      -  "price_time",
      -  "notes",
      -  "state",
      -  "taxable",
      -  "threshold_usd",
      -  "rule_text",
      -  "estimate_tax",
      -  "disclaimer"
      -]New value: +[
      +  "source_url",
      +  "price_time",
      +  "notes",
      +  "state",
      +  "taxable",
      +  "threshold_usd",
      +  "rule_text",
      +  "estimate_tax",
      +  "can_checkout_online",
      +  "warnings",
      +  "disclaimer"
      +]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description is not carrying the safety burden. It still adds real context beyond them: the result is an estimate only, authoritative tax appears at checkout, the response includes a state page link, and it is explicitly not tax advice — which matters for how an agent should relay the output.

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 first sentence front-loads what is returned and the trigger sentence follows shortly after. Slightly dense with three clauses stacked in the opening sentence, but every clause carries information and nothing is 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?

With a full output schema the description need not explain return values, yet it still flags the state page link and the estimate caveat. For a four-parameter, read-only lookup tool this covers what an agent needs; only minor details such as behavior for unsupported or non-US states are unaddressed.

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 coverage is 100% and every parameter already has a description and enums, so the baseline of 3 applies. The description hints at the semantics of 'amount' (an estimate for an order amount) but adds no format, rounding, or boundary guidance beyond what the schema states.

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 names a concrete verb+resource ('Estimate sales tax') and spells out exactly what the result contains: whether the state taxes bullion, any threshold, and an estimate for a given order amount. No sibling tool covers tax, so an agent can tell unambiguously that this is the tax-lookup tool rather than a pricing or checkout tool.

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?

'Use when the user asks about US sales tax on a bullion purchase' gives an explicit trigger condition, and it implicitly routes final-tax questions to checkout ('the final tax is shown at checkout'). It stops short of an explicit when-not statement, but the estimate-vs-final split effectively covers the main misuse case.

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.

Resources