Skip to main content
Glama
jackdark425

Financial Modeling Prep (FMP) MCP Server

by jackdark425

search_symbol

Find stock symbols using company names or tickers to identify securities for financial analysis and market tracking.

Instructions

Search for stock symbols by company name or ticker

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query (company name or ticker)

Implementation Reference

  • The handler implementation and registration for 'search_symbol' tool.
    // Search Symbol
    server.registerTool(
      'search_symbol',
      {
        description: 'Search for stock symbols by company name or ticker',
        inputSchema: SearchSchema,
      },
      async (args: z.infer<typeof SearchSchema>) => {
        try {
          const data = await fetchFMP(`/search-symbol?query=${encodeURIComponent(args.query)}&limit=10`);
          return jsonResponse(data);
        } catch (error) {
          return errorResponse(error);
        }
      }
    );
  • Input schema definition for the 'search_symbol' tool.
    const SearchSchema = z.object({
      query: z.string().describe('Search query (company name or ticker)'),
    });
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 is for searching, implying a read-only operation, but doesn't cover aspects like rate limits, authentication needs, error handling, or what the search returns (e.g., list of symbols with details). This is a significant gap for a tool with no annotation coverage.

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 a single, efficient sentence that front-loads the core purpose without unnecessary words. Every part earns its place by specifying the action, resource, and search criteria, making it appropriately sized for the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (search function with one parameter), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what the search returns (e.g., format, fields), potential errors, or behavioral traits like pagination or rate limits, leaving gaps for an agent to use it effectively.

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 minimal meaning beyond the input schema, which has 100% coverage and documents the single parameter 'query' as 'Search query (company name or ticker)'. The description restates this but doesn't provide additional context like query syntax, examples, or limitations. With high schema coverage, the baseline is 3.

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 with a specific verb ('search') and resource ('stock symbols'), and specifies what can be searched ('by company name or ticker'). However, it doesn't explicitly differentiate from sibling tools like 'get_quote' or 'get_company_profile', which might also involve stock symbols but serve different purposes.

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 prerequisites, such as needing a query, or compare it to siblings like 'get_quote' (for price data) or 'get_company_profile' (for detailed info), leaving the agent to infer usage context.

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/jackdark425/aigroup-fmp-mcp'

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