Skip to main content
Glama

Profit / Loss Calculator

calculator_profit_loss
Read-only

Profit or loss amount and percentage from cost and selling 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": {
      "cost_price": "<cost_price>",
      "selling_price": "<selling_price>"
    },
    "name": "calculator_profit_loss"
  }
}

Input Schema

NameRequiredDescriptionDefault
cost_priceYesCost price.
selling_priceYesSelling price.

Output Schema

NameRequiredDescriptionDefault
amountNo
statusYes
expressionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description confirms it is a pure derivation from the two prices but adds nothing about edge cases such as selling price below cost yielding a negative result, or division-by-zero when cost is zero.

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?

A single front-loaded sentence that states outputs first and inputs second, with zero filler. It is a sentence fragment rather than a full clause, which slightly reduces readability but not information density.

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 two-parameter pure calculator with an output schema and full annotation coverage, the description gives what is needed to call it correctly. Only the sign convention for a loss and the zero-cost case remain unspecified, which is minor here.

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% and both properties are typed and exampled, so the description contributes nothing beyond the schema. The phrase 'from cost and selling price' only restates the parameter names. Baseline 3 applies.

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 names a specific computation (profit/loss amount and percentage) and its two inputs (cost and selling price), which is enough to tell it apart from adjacent siblings like calculator_percentage_change or calculator_discount. It omits an explicit verb, but the resource and output are unambiguous.

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?

There is no statement of when to pick this over calculator_percentage_change, calculator_discount, or calculator_investment, and no exclusions or prerequisites. The agent must infer selection from the input names alone.

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.