Skip to main content
Glama

minia2a — hosted x402 API marketplace (HTTP)

x402-tax-calc

Tax Calc: Calculate tax on an amount. Provide amount and rate (or taxRate); supports rate modes via the mode parameter. 🆓 5 free trial calls per signed wallet

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "x402-tax-calc"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo
rateNo
amountNo
taxRateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / amount / description
      Removed value: -"Amount to process"
    • removedInput schema / properties / mode / description
      Removed value: -"Mode to process"
    • removedInput schema / properties / rate / description
      Removed value: -"Rate to process"
    • removedInput schema / properties / taxRate / description
      Removed value: -"TaxRate to process"
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does not state whether the rate is a percent or a decimal fraction, what the valid 'mode' values are, whether tax is added or extracted, or what the response contains. The only behavioral disclosure is the payment context ('5 free trial calls per signed wallet'), which is useful but orthogonal to how the computation behaves.

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?

Three short sentences, purpose front-loaded, input requirements immediately after. The trial-call note is arguably a pricing blurb rather than tool guidance, but it is one clause and does not obscure the operational content.

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

Completeness2/5

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

A four-parameter calculator with no annotations, no output schema and 0% parameter documentation should explain the rate unit, the allowed mode values, and at least the shape of the result. None of these are present, so an agent would have to guess at semantics that materially change the computed tax.

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 description coverage is 0% across four parameters, so the description must compensate. It does clarify that 'rate' and 'taxRate' are alternative synonyms and that 'mode' selects a rate mode, which is real added meaning. However, it never enumerates the mode values, and the rate vs taxRate precedence when both are sent (and the unit of rate) is left undefined, leaving significant ambiguity in a zero-coverage schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Calculate tax on an amount.' An agent can tell this apart from percent/percentage-change siblings. It stops short of full disambiguation (e.g. vs x402-percent-of or x402-vat-validate) but the core purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description tells the agent what inputs to supply ('Provide amount and rate (or taxRate)'), which implies when the tool applies, but gives no explicit when-to-use/when-not-to-use guidance or named alternative for related percentage/VAT tools. Usage is inferred rather than stated.

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.