Skip to main content
Glama

Proving Ground: closed trades, wins and losses

decision_journal
Read-onlyIdempotent

INDICIA DESK's decision journal: options strategies tracked at real Deribit bid/ask prices (paper account), with every closed trade, wins and losses. Returns per-strategy trade counts, win rate and average result, and the latest closed trades. Use to show how rule-based options strategies actually performed. Live entry signals and exact structures are not available here.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "decision_journal"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetNoUnderlying asset.
limitNo
strategyNoPart of a strategy name, e.g. "Skew", "Fear Spike". Omit to list all.

Output Schema

NameRequiredDescriptionDefault
linkYes
as_ofYesUTC time the underlying data was computed.
staleYesTrue when the data is older than its normal refresh cycle.
caveatNo
sourceNo
summaryYes
age_hoursNoHours between as_of and the time of this answer.
disclaimerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / age_hours
      Added value: +{
      +  "description": "Hours between as_of and the time of this answer.",
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuinely non-structured context: prices are real Deribit bid/ask on a paper account, and results are limited to closed trades only, which matters for interpreting the numbers.

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 sentences, front-loaded with the resource and immediately followed by the return shape and the exclusion. Minor brand framing ('INDICIA DESK's') and paper-account phrasing could be tighter, but nothing is redundant.

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?

An output schema exists, so return-value detail needn't be spelled out, and annotations cover safety. The description still supplies the data provenance and the closed-trades-only scope an agent needs to interpret results correctly; only pagination/ordering of 'latest' is left implicit.

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 67% – asset and strategy are documented in the schema, but limit is undescribed there. The description only indirectly hints that limit governs 'the latest closed trades'; it adds nothing about the strategy substring matching that the schema already explains. Baseline 3 for middling coverage with no real gain.

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 specific resource (decision journal of closed options-strategy trades) and what it returns (per-strategy trade counts, win rate, average result, latest closed trades). It also carves out a boundary against live-signal tooling, so an agent can tell it apart from hypothesis_ledger, though no sibling is named explicitly.

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?

'Use to show how rule-based options strategies actually performed' gives a clear use case, and the closing sentence explicitly excludes live entry signals and exact structures. There is no explicit statement of when to prefer a sibling or what prerequisite state exists, so it stops short of a 5.

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