Scientific Calculator

Discount Calculator

calculator_discount

Read-only

Discount amount and final price, or reverse original from sale price.

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": {
      "discount": "<discount>"
    },
    "name": "calculator_discount"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	No	forward or reverse.	forward
`discount`	Yes	Discount percentage 0–100.
`original_price`	No	Original/MRP (forward mode).
`discounted_price`	No	Sale price (reverse mode).

Output Schema

Name	Required	Description	Default
`expression`	Yes
`final_price`	Yes
`discount_amount`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already establish that this is a read-only, non-destructive, closed-world calculator. The description adds that it returns discount amount and final price or reverses an original price, but it does not mention rounding, validation behavior, or mode-specific requirements.

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?

It is a single short line with no filler and front-loads the calculated outputs. The structure is slightly fragmentary and lacks an explicit verb, which keeps it from being fully polished.

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 simple read-only calculator with full schema description coverage, annotations, and an output schema, the description is largely complete. It covers both forward and reverse operations, though mode-specific usage could be clearer.

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 all four parameters are already documented, including mode, discount, original_price, and discounted_price. The description aligns with the reverse-price concept but does not add parameter-level meaning beyond the 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?

The description identifies a discount calculation and names two outcomes: discount amount/final price and reversing original from sale price. It is clear enough to distinguish from most siblings, but it does not explicitly contrast with nearby tools such as calculator_percentage or calculator_gst.

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

Usage Guidelines2/5

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

It implies forward and reverse modes but gives no explicit guidance on when to use each mode, required inputs per mode, or alternatives to this tool. The agent must infer usage entirely from the schema.

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

All Scientific Calculator tools Inspect

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.