Qanvo Stock Screener

My option positions

my_option_positions

Read-onlyIdempotent

The user's open option positions across every connected broker, priced now (mark, underlying, moneyness, intrinsic/extrinsic, premium captured, breakeven, delta, IV, theta/day, dollar delta, coverage, earnings/ex-dividend before expiry) plus portfolio totals (net theta, dollar delta, vega, short premium open vs cost to close).

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_positions"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	No	Optional underlying ticker.
`account`	No	Optional account key (A1, A2...).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 3, 2026

addedInput schema / properties / account

Added value: +{
+  "default": null,
+  "description": "Optional account key (A1, A2...).",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedInput schema / properties / symbol

Added value: +{
+  "default": null,
+  "description": "Optional underlying ticker.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

AddedNov 2, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds meaningful behavioral context: aggregation across every connected broker, real-time pricing ('priced now'), and the specific valuation and portfolio-total fields returned. It does not discuss data freshness limits, broker-connection requirements, or empty states.

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?

It is a single front-loaded sentence with no filler, and the parenthetical field list is information-dense. The list is long and could be harder to scan, 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?

For a read-only tool with no output schema, the description does a good job of enumerating the return payload, including portfolio totals. It is slightly incomplete on filtering behavior and edge cases, but the schema covers the two parameters.

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 100% and both optional filters are documented in the input schema. The description does not explain how symbol or account affect the result, so it neither adds nor detracts; 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?

The description identifies the resource precisely ('open option positions across every connected broker') and enumerates the metrics returned, making it distinguishable from order- and trade-oriented siblings. It does not explicitly name a sibling to use instead, so it stops short of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given, and none of the siblings (e.g., my_portfolio, my_option_orders, my_closed_option_trades) are referenced. The agent must infer that this is the live-position view rather than an order, history, or payoff tool.

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?