Skip to main content
Glama
Open-Agent-Tools

Open Stocks MCP

by Open-Agent-Tools
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

option_debit_spread

Place a debit spread order by buying a long option and selling a short option. Specify instrument IDs, quantity, and net debit price.

Instructions

Places a debit spread order (buy long option, sell short option).

Args:
    short_instrument_id: The option instrument ID to sell (short leg)
    long_instrument_id: The option instrument ID to buy (long leg)
    quantity: The number of spread contracts
    debit_price: The net debit paid per spread

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
short_instrument_idYes
long_instrument_idYes
quantityYes
debit_priceYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It does not disclose behavioral traits beyond the order type, such as permissions, risk, or impact.

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?

Description is concise and front-loaded with the main purpose. Every sentence is functional, but the Args block could be integrated more naturally.

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?

The description explains the tool's action and parameters, but lacks usage context, behavioral details, and explanation of the output. With 4 required parameters and an output schema, more completeness would be beneficial.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Parameters are listed with minimal explanations that essentially repeat the schema titles. Given 0% schema description coverage, the description should add more detail than it does.

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?

Description clearly states 'Places a debit spread order (buy long option, sell short option).' This verb+resource definition is specific and distinguishes from the sibling tool 'option_credit_spread'.

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 guidance on when to use this tool versus alternatives, nor any prerequisites or contexts. The description lacks information on typical scenarios or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Open-Agent-Tools/open-stocks-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server