Skip to main content
Glama

BRAINIAC Crypto Tax Computation

Derivatives realised P/L

crypto-tax_derivatives-pnl
Read-onlyIdempotent

Compute realised P/L for linear perpetuals/futures and options including fees and funding from caller trade inputs. Price $0.03 USDC. POST /api/v1/crypto-tax/derivatives-pnl. An unpaid call returns the x402 payment terms and does not run.

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": {
      "trades": "<trades>"
    },
    "name": "crypto-tax_derivatives-pnl"
  }
}

Input Schema

NameRequiredDescriptionDefault
tradesYestrades, array. Required.

Output Schema

NameRequiredDescriptionDefault
totalNototal. Number.
tradesNotrades. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavior: a $0.03 USDC price and the fact that an unpaid call returns x402 payment terms without executing. Combined with "from caller trade inputs" (no external data fetch), this is well beyond what the annotations convey.

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?

Three tight sentences, front-loaded with the compute action, then cost, then endpoint and payment fallback. No wasted wording; the endpoint path is arguably redundant but harmless for an HTTP-based tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need not be explained, and payment mechanics are covered. However, for a financial calculation tool, the description omits calculation conventions (e.g., how options premium/settlement enter P/L, sign conventions for funding) that an agent might need to supply correct inputs.

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% with a single documented `trades` array, so the baseline is 3. The description adds marginal meaning by naming fees and funding as included in the calculation and clarifying that trade data is caller-supplied, but it does not explain instrument-specific requirements such as premium for options or settlementValue use.

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?

States a concrete verb and resource: "Compute realised P/L for linear perpetuals/futures and options" and specifies the input source (caller trade inputs). This is specific enough for an agent to distinguish it from sibling tax tools like cost-basis-lots or us-form-8949-rows, though it never names a sibling to route against.

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

Usage Guidelines3/5

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

Usage is implied by the instrument scope (linear perpetuals/futures and options) rather than stated as explicit conditions. There is no when-not guidance or naming of alternatives such as unrealized-snapshot for open positions, so the agent must infer fit from the scope 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.

Resources