Hopi

Crypto profit calculator

hopi_crypto_profit_calculator

Read-onlyIdempotent

Work out profit or loss on a crypto trade from buy price, quantity and an optional per-side fee percentage. Returns breakeven price always, and profit, return percentage and total fees once a sell price is given. All figures are treated as GBP. Source: https://hopi.co.uk/crypto-profit-calculator/

Input Schema

TableJSON Schema

Name	Required	Description
`buy`	Yes	Buy price per unit
`fee`	No	Fee percentage charged on each side (default 0, must be 0 to under 100)
`sell`	No	Sell price per unit (optional; omit to see breakeven only)
`quantity`	Yes	Quantity of coin traded

Output Schema

TableJSON Schema

Name	Required	Description
`profit`	No
`summary`	Yes
`breakeven`	Yes
`totalFees`	No
`source_url`	Yes	The tool's page on hopi.co.uk (cite or open to check the figure)
`profitString`	No
`returnPercent`	No
`breakevenString`	Yes
`totalFeesString`	No
`returnPercentString`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

addedOutput schema / required

Added value: +[
+  "breakeven",
+  "breakevenString",
+  "source_url",
+  "summary"
+]

First observedSep 20, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already mark this read-only, idempotent, and non-destructive. The description adds valuable behavioral detail beyond annotations: breakeven is always returned, profit/return percentage/total fees appear only when a sell price is provided, and all figures are in GBP. This gives the agent a clear model of output behavior without contradicting the annotations.

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?

The description is three tight sentences with no filler. It front-loads the core action, then explains conditional outputs and currency, and ends with a source reference. Every sentence contributes useful information.

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?

For a calculator tool with two required and two optional parameters, the description covers inputs, the optional-dependent output behavior, currency, and source. An output schema exists to describe return values in more detail, so nothing essential is missing.

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 parameters are already documented. The description adds useful extra semantics: the fee is 'per-side,' sell price is optional and controls which outputs appear, and currency is GBP. These nuances go beyond the schema's basic field descriptions.

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 clearly states the specific operation—'work out profit or loss on a crypto trade'—and identifies the exact inputs: buy price, quantity, and optional per-side fee. This distinguishes it from the many other calculator-type sibling tools by focusing on trade P&L rather than position sizing, staking, or DCA.

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?

The description gives clear context for when to use the tool: whenever a crypto trade profit/loss needs calculating, with optional sell price for full results and omission for breakeven only. It does not explicitly name alternatives or state when not to use it, but the purpose is specific enough that an agent can route correctly among the large sibling set.

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

All Hopi 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.

Resources

Need Help?