EarningsWatcher

Paper Trade

paper_trade

Save/track an options position on your account (this is exactly what the app's 'Paper Trade' button does — it appears in your positions and journal). Provide legs as {id, qty} using contract ids from options_chain / atm_contracts / guided_positions; quantities are supported. Entry price and category are auto-derived from the chain if you don't pass them.

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": {
      "symbol": "<symbol>"
    },
    "name": "paper_trade"
  }
}

Input Schema

Name	Required	Description
`symbol`	Yes	Stock ticker symbol, e.g. AAPL.
`category`	No	Trade category label. Auto-set from the position's long/short-vol direction if omitted.
`long_puts`	No	Long put legs.
`long_calls`	No	Long call legs.
`short_puts`	No	Short put legs.
`description`	No	Optional thesis/notes for the trade.
`entry_price`	No	Net entry premium (debit positive, credit negative). Auto-computed from the chain if omitted.
`short_calls`	No	Short call legs.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the mutation profile is covered. The description adds real value beyond that: it discloses the side effect (record appears in positions and journal) and the auto-derivation of entry price and category when omitted. It doesn't address duplicate handling or error behavior, keeping it from a 5.

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 dense sentences with no filler, and the purpose is front-loaded before the input-format guidance. The parenthetical is slightly chatty but carries informative content rather than padding.

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 an 8-parameter mutation tool with no output schema, the description covers purpose, id provenance, leg shape, and auto-derivation defaults — enough to invoke it correctly. It doesn't describe the response or what validates on entry, which is the only minor gap.

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?

Schema coverage is 100%, so the baseline is 3, but the description goes further by explaining the leg format ({id, qty}), that quantities are supported, where ids come from, and that entry_price and category are auto-derived if not passed. That added meaning lifts it above the schema-only baseline.

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?

States a specific verb and resource (save/track an options position) and grounds it in concrete app behavior ('exactly what the app's Paper Trade button does — it appears in your positions and journal'). This clearly separates it from siblings like close_paper_trade, paper_positions, and live trade tools.

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?

Explains the context of use (recording a paper position that shows in positions and journal) and names the upstream tools that supply contract ids (options_chain / atm_contracts / guided_positions), which is a meaningful routing hint. It lacks an explicit 'when-not to use' or a pointer to the closing sibling, 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.

All EarningsWatcher tools Inspect

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

Need Help?