Skip to main content
Glama
tresor4k

macalc

calculate_crypto_profit_loss

Calculate cryptocurrency trading profit or loss including transaction fees. Input buy price, sell price, quantity, and optional fee percentages to get net P&L, ROI percentage, and break-even price.

Instructions

Compute crypto trading profit/loss including fees. Use for crypto investors tracking realized P&L. Inputs: buy price, sell price, quantity, buy fee, sell fee. Returns net P&L, ROI %, break-even price. See list_bundles for related 'crypto' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
buy_priceYesPurchase price per unit in fiat currency
sell_priceYesSale price per unit in fiat currency
quantityYesQuantity of cryptocurrency traded
buy_fee_pctNoBuy transaction fee percentage (default 0.1%)
sell_fee_pctNoSell transaction fee percentage (default 0.1%)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoComputed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses that fees are included and lists outputs, but lacks details on edge cases (e.g., negative prices), precision, or side effects. This is adequate but not comprehensive.

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 two sentences with no redundancy. First sentence states core purpose, second provides usage and cross-reference. Every word earns its place.

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 calculation tool with many siblings and an output schema (not shown), the description is fairly complete. It identifies target users, inputs/outputs, and related tools. Could mention that it works with fiat currencies or any unit, but overall sufficient.

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%, so baseline is 3. The description lists parameter names but adds no additional meaning beyond the schema's field descriptions. For example, it does not clarify units or constraints not already in the schema.

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 states 'Compute crypto trading profit/loss including fees' which is a specific verb and resource. It clearly distinguishes from sibling calculators like 'calculate_crypto_tax_fr' or 'calculate_impermanent_loss' by focusing on realized P&L with fees.

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 explicitly says 'Use for crypto investors tracking realized P&L', providing clear context. It also references 'list_bundles' for related tools, but does not include when-not-to-use or alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tresor4k/macalc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server