Skip to main content
Glama

TradingCalc MCP — Crypto Futures Math

by io.github.SKalinin909
OverviewDiscussionsAdmin

workflow.run_scenario_planning

Run a scenario analysis: compute PnL for multiple price-change percentages at once. Use when user asks "show me my P&L if BTC moves -10%, -5%, +5%, +10%". Returns: array of { deltaPct, exitPrice, netPnl, roe }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sideYes
sizeYesPosition size in base asset
deltasPctYesList of price change percentages, e.g. [-10, -5, 0, 5, 10]
entryPriceYesEntry price
feeOpenPctNoOpening fee fraction
feeClosePctNoClosing fee fraction
contractTypeNolinear = USDT-margined (default), inverse = coin-margined. For inverse, size is USD contracts and pnl/fees come out in the base coin.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / contractType
      Added value: +{
+  "description": "linear = USDT-margined (default), inverse = coin-margined. For inverse, size is USD contracts and pnl/fees come out in the base coin.",
+  "enum": [
+    "linear",
+    "inverse"
+  ],
+  "type": "string"
+}
  2. Added

TDQS

A4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It implies a pure computation by saying 'compute PnL', but it never explicitly states that this is read-only, does not place orders, or has no side effects.

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 concise and directly structured: purpose, example trigger, and return shape. It avoids unnecessary detail while covering the essential information an agent needs.

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?

Given the moderate complexity and absence of an output schema, the description appropriately includes the return array structure. It does not discuss edge cases, but the provided example and schema descriptions are sufficient for typical use.

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?

The schema covers most parameters with descriptions, and the tool description adds useful context by defining the return fields. The 'side' parameter lacks a description, but its enum values 'long'/'short' are self-explanatory, so the overall parameter meaning is well conveyed.

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?

Description clearly states the tool's purpose: 'Run a scenario analysis: compute PnL for multiple price-change percentages at once.' It differentiates from sibling workflows by emphasizing multiple price-change scenarios in one call, and gives a concrete example user query.

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 provides an explicit trigger example: 'Use when user asks "show me my P&L if BTC moves -10%, -5%, +5%, +10%"' and explains the return shape. It does not explicitly name sibling alternatives or state when not to use this tool, but the usage context is clear enough.

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

All TradingCalc MCP — Crypto Futures Math toolsInspect
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