Skip to main content
Glama

Tax-Inclusive Price Split

bpj_reverse_sales_tax
Read-onlyIdempotent

Back out the pre-tax amount and tax from a gross price and a user-supplied tax rate.

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": {
      "gross": "<gross>",
      "rate": "<rate>"
    },
    "name": "bpj_reverse_sales_tax"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateYes
grossYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered. The description adds only that the rate is user-supplied, which implies no lookup table or jurisdiction logic; it says nothing about rounding/precision of the backed-out amounts or behavior at rate=0.

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?

A single front-loaded sentence that states the operation and both inputs with no filler. Nothing could be removed without losing meaning.

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?

For a two-parameter arithmetic utility with full annotations, the description covers the operation and the inputs and even names the two outputs (pre-tax amount and tax). It omits rounding behavior and the percent-vs-decimal convention, which are the main failure modes for a tax-split tool.

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 description coverage is 0%, so the description must carry the semantic load, and it does identify both parameters by role: "gross" as the tax-inclusive total and "rate" as a user-supplied tax rate. It stops short of stating that the rate is a percentage (only the schema title conveys that) and says nothing about allowed bounds or precision.

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?

The description gives a specific verb phrase ("back out the pre-tax amount and tax") and names both inputs (gross price, tax rate), so the operation is unmistakable. It does not distinguish itself from any sibling, but no sibling in the visible list performs a comparable tax split, so ambiguity risk is low.

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?

Usage is implied by the phrase "gross price and a user-supplied tax rate" – an agent can infer this is for tax-inclusive pricing where the rate is known. There is no explicit when-to-use/when-not statement and no mention of the natural alternative (a forward tax calculation, if one existed).

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.