Skip to main content
Glama
jjmerri

E*TRADE MCP Server

by jjmerri

etrade_lookup_product

Search for stocks, mutual funds, and options using symbols or company names to retrieve detailed product information from E*TRADE market data.

Instructions

Look up products by symbol or company name.

Args: search: Full or partial symbol name to search for company: Full or partial company name (optional) type: Security type - EQ (equity), MF (mutual fund), OPTN (option) (optional)

Returns: List of matching products with details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchYes
companyNo
typeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main etrade_lookup_product tool handler function, registered via @mcp.tool() decorator in FastMCP. It authenticates via get_market_client() and delegates the lookup to MarketClient.look_up_product() method.
    @mcp.tool()
    def etrade_lookup_product(search: str, company: Optional[str] = None,
                              type: Optional[str] = None) -> dict:
        """
        Look up products by symbol or company name.
        
        Args:
            search: Full or partial symbol name to search for
            company: Full or partial company name (optional)
            type: Security type - EQ (equity), MF (mutual fund), OPTN (option) (optional)
            
        Returns:
            List of matching products with details
        """
        client = get_market_client()
        return client.look_up_product(search, company, type)
  • The core helper method in MarketClient class that performs the actual E*TRADE API request to /v1/market/lookup/{search}.json with optional company and type parameters, handling the HTTP GET and response parsing.
    def look_up_product(self, search: str, company: Optional[str] = None,
                       type: Optional[str] = None) -> Dict[str, Any]:
        """
        Look up products (stocks, options, mutual funds)
        
        Args:
            search: Full or partial symbol name
            company: Full or partial company name
            type: Security type (e.g., EQ for equity, MF for mutual fund, OPTN for option)
            
        Returns:
            Product lookup response data
        """
        url = f"{self.base_url}/v1/market/lookup/{search}.json"
        
        params = {}
        if company:
            params["company"] = company
        if type:
            params["type"] = 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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool returns a list of matching products but doesn't mention critical aspects like authentication requirements (implied by sibling tools), rate limits, error handling, or whether this is a read-only operation. The description is minimal and lacks behavioral context.

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?

The description is well-structured with a clear purpose statement followed by Args and Returns sections. It's concise with no wasted sentences, though the lack of usage guidelines or behavioral details means it could be more informative without sacrificing brevity.

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?

Given the tool has an output schema (which covers return values), the description doesn't need to detail returns. However, with 3 parameters, 0% schema coverage, and no annotations, the description only partially compensates. It explains parameters but misses authentication needs, error cases, and sibling differentiation, making it incomplete for safe and effective use.

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?

The description adds some parameter semantics beyond the schema, which has 0% coverage. It explains that 'search' is for symbol names, 'company' for company names, and 'type' for security types with examples (EQ, MF, OPTN). However, it doesn't clarify if searches are case-sensitive, the format of returns, or how partial matches work, leaving gaps in understanding.

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 as 'Look up products by symbol or company name,' which is a specific verb+resource combination. However, it doesn't explicitly differentiate this from sibling tools like etrade_get_quote, which might also retrieve product information, leaving room for potential confusion about when to use each.

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 like etrade_get_quote or other siblings. It mentions optional parameters but doesn't explain scenarios where searching by symbol vs. company name is preferred or how this tool complements others in the server.

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