Skip to main content
Glama
jjmerri

E*TRADE MCP Server

by jjmerri

etrade_get_option_expire_dates

Retrieve available option expiration dates for any stock symbol, filtering by weekly, monthly, quarterly, or all expirations to support options trading decisions.

Instructions

Get option expiration dates for a symbol.

Args: symbol: Underlying stock symbol (e.g., "AAPL") expiry_type: WEEKLY, MONTHLY, QUARTERLY, or ALL (optional)

Returns: List of available expiration dates for options

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes
expiry_typeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler function decorated with @mcp.tool(). Delegates to MarketClient.get_option_expire_dates after ensuring authentication.
    @mcp.tool()
    def etrade_get_option_expire_dates(symbol: str, expiry_type: Optional[str] = None) -> dict:
        """
        Get option expiration dates for a symbol.
        
        Args:
            symbol: Underlying stock symbol (e.g., "AAPL")
            expiry_type: WEEKLY, MONTHLY, QUARTERLY, or ALL (optional)
            
        Returns:
            List of available expiration dates for options
        """
        client = get_market_client()
        return client.get_option_expire_dates(symbol, expiry_type)
  • Core implementation in MarketClient class that makes the authenticated HTTP GET request to E*TRADE's /v1/market/optionexpiredate.json endpoint with the symbol and optional expiry_type parameters.
    def get_option_expire_dates(self, symbol: str, expiry_type: Optional[str] = None) -> Dict[str, Any]:
        """
        Get option expiration dates for a symbol
        
        Args:
            symbol: Underlying symbol
            expiry_type: Expiry type (WEEKLY, MONTHLY, QUARTERLY, ALL)
            
        Returns:
            Expiration dates response data
        """
        url = f"{self.base_url}/v1/market/optionexpiredate.json"
        
        params = {"symbol": symbol}
        if expiry_type:
            params["expiryType"] = expiry_type
        
        response = self.session.get(url, params=params)
        response.raise_for_status()
        
        return response.json()
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'Get[s]' data, implying a read-only operation, but doesn't address other behavioral aspects like authentication requirements, rate limits, error handling, or whether it's idempotent. For a tool with no annotation coverage, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded: the first sentence states the purpose clearly, followed by structured sections for 'Args' and 'Returns'. Every sentence adds value without redundancy, making it efficient and easy to parse.

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?

Given the tool's low complexity (2 parameters, no nested objects) and the presence of an output schema (which covers return values), the description is mostly complete. It explains parameters well, but lacks context on usage guidelines and behavioral traits, which slightly reduces completeness for agent invocation.

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

Parameters4/5

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

The description adds meaningful context beyond the input schema. The schema has 0% description coverage, but the description explains 'symbol' as 'Underlying stock symbol (e.g., "AAPL")' and 'expiry_type' with allowed values ('WEEKLY, MONTHLY, QUARTERLY, or ALL') and notes it's optional. This compensates well for the schema's lack of documentation.

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 clearly states the tool's purpose: 'Get option expiration dates for a symbol.' It specifies the verb ('Get') and resource ('option expiration dates'), and the scope ('for a symbol') is clear. However, it doesn't explicitly differentiate from sibling tools like 'etrade_get_option_chains' or 'etrade_lookup_product', which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'etrade_get_option_chains' or 'etrade_lookup_product', nor does it specify prerequisites such as authentication. This leaves the agent with minimal context for tool selection.

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/jjmerri/etrade-mcp'

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