Skip to main content
Glama

screen wheel strategy options

screen_wheel_strategy_options
Read-only

Screen cash-secured puts or covered calls on a US stock (options expiring in 3 to 9 days) and get an OPEN or SKIP decision, using the Wheel-strategy Option Desk on Finch. Returns the agent's official description, price, free runs, a run link and a ready-to-send request.

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

Input Schema

NameRequiredDescriptionDefault
taskNoOptional short description of what the user wants. Do not include private documents or secrets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description usefully adds that it is an external Finch desk plus cost signals (price, free runs). However it never resolves whether calling it actually executes the screen and yields the OPEN/SKIP verdict, or merely hands back a 'ready-to-send request' the agent must dispatch elsewhere - a significant behavioral ambiguity for a tool whose name promises a decision.

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?

Front-loaded with the verb, resource and scope, and the return payload is summarized in one clause. Slightly dense, but every clause carries information.

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?

No output schema exists, and while the description lists the return fields, it leaves the crucial execution model unexplained - whether the OPEN/SKIP decision is produced by this call or by a subsequent send step using the returned request. For a tool that appears to be an agent-dispatch wrapper, that gap matters.

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?

There is a single optional parameter with 100% schema description coverage, so the schema already carries the meaning. The description says nothing about the `task` parameter, so baseline 3 applies.

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 (screen), specific instruments (cash-secured puts / covered calls), a scope constraint (US stocks, 3-9 day expiries), and the decision output (OPEN or SKIP). No sibling tool touches options screening, so an agent can route to it unambiguously.

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 domain constraints (US stock, wheel strategy, 3-9 DTE options) make it clear when this applies, but there is no explicit when-not guidance or named alternative among the siblings.

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.