EarningsWatcher

Guided Positions

guided_positions

Read-only

The platform's full 'guide me' catalog of concrete, ready-to-build option structures for a symbol and view — the specific straddles/strangles/butterflies/condors (or directional debit/credit spreads) per expiration, with their breakevens, P&L scenarios and price. Each result includes parsed legs you can pass straight to simulate_position / simulate_pnl / paper_trade.

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": "guided_positions"
  }
}

Input Schema

Name	Required	Description	Default
`view`	No	bullish/bearish = directional; non_dir_long = long vol; non_dir_short = short vol.	non_dir_long
`symbol`	Yes	Stock ticker symbol, e.g. AAPL.
`category`	No	Structure category. long_vol: 'straddle / strangles' \| 'inverse butterflies'; short_vol: 'short straddle / strangles' \| 'butterflies'; bullish/bearish: 'long' \| 'short'. Defaults to the first.
`expiration`	No	Expiration label (from the returned list). Defaults to the first.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 28, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds genuine context beyond that: results carry breakevens, P&L scenarios, price, and parsed legs that plug directly into simulate_position/simulate_pnl/paper_trade. Pagination/limits for a catalog endpoint remain undisclosed.

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?

Two sentences, front-loaded with the core resource and followed by the concrete result content. Dense but every clause carries information; no filler or restating of the title.

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?

With no output schema, the description does the work of describing return values (breakevens, P&L scenarios, price, parsed legs), which is exactly what an agent needs. Missing only edge-case behavior such as an empty catalog for a symbol and how defaults resolve when category/expiration are omitted.

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%, including enum semantics for view and default behavior for category/expiration, so the schema carries the burden. The description only loosely ties inputs to 'a symbol and view' and adds no syntax or format detail beyond what the schema already documents; 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?

States a specific verb+resource: a curated catalog of concrete option structures (straddles/strangles/butterflies/condors, directional spreads) per expiration for a symbol and view. It distinguishes itself from downstream tools (simulate_position, simulate_pnl, paper_trade) by noting the legs are passable to them, but doesn't contrast against semantically similar siblings like pick_position, suggest_position, or guide.

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 — you call this when you want ready-to-build, pre-computed structures for a symbol/view. There is no explicit when-not guidance and no comparison to the adjacent 'pick a position' tools (pick_position, suggest_position, guide), which an agent would need to route between.

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?