Qanvo Stock Screener

My option orders & premiums

my_option_orders

Read-onlyIdempotent

The user's option orders with premiums in dollars (credit +, debit -): action, contract, contracts, fill price, status, times, plus totals (credits, debits, net premium, by underlying, by day). Up to 90 days live from the brokerages; longer from synced fills. Read-only: Qanvo never places orders.

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

Input Schema

Name	Required	Description	Default
`days`	No	Look-back days: 1-90 live, up to 3650 from history. Default 30.
`side`	No	all, sell (credits) or buy (debits). Default all.	all
`status`	No	all, filled or working. Default all.	all
`symbol`	No	Optional underlying ticker.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 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 and destructiveHint=false, and the description usefully reinforces the safety profile with 'Qanvo never places orders'. More valuable is the disclosure of the two data provenances (live brokerage window vs. synced historical fills) and the premium sign convention (credit +, debit -), which the annotations cannot express.

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 resource and its premium semantics, with the coverage caveat and read-only guarantee following in the order an agent needs them. Dense enumeration of fields is efficient rather than padded.

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?

No output schema exists, so the description carries the return-shape burden and does so by naming the returned fields and the available totals (credits, debits, net premium, by underlying, by day). Together with the read-only note and the data-coverage window, an agent has enough to call it correctly; only explicit sibling routing is missing.

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%, so each of days, side, status and symbol is already documented, including the 1-90 live / up to 3650 history range. The description adds only the premium sign convention and total breakdowns, which are output-side rather than parameter meaning. Baseline 3 holds.

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 (the user's option orders) and enumerates what comes back – action, contract, contracts, fill price, status, times, plus premium totals. The 'option' qualifier plus the premium framing implicitly separates it from the equity sibling my_orders and from my_closed_option_trades, 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 Guidelines3/5

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

Gives a usable data-coverage rule ('Up to 90 days live from the brokerages; longer from synced fills') that tells the agent what to expect for a given look-back. It never states when to prefer this over my_orders, my_closed_option_trades, or my_option_positions, so routing between siblings is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Qanvo Stock Screener 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?