Skip to main content
Glama
jackdark425

Financial Modeling Prep (FMP) MCP Server

by jackdark425

get_company_profile

Retrieve detailed company profiles including description, industry, sector, CEO, and key business information using stock ticker symbols for financial analysis and research.

Instructions

Get detailed company profile information including description, industry, sector, CEO, and more

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesStock ticker symbol

Implementation Reference

  • The handler function for get_company_profile which fetches data from the FMP API.
    async (args: z.infer<typeof CompanyProfileSchema>) => {
      try {
        const data = await fetchFMP<CompanyProfile[]>(`/profile?symbol=${args.symbol.toUpperCase()}`);
        return jsonResponse(data);
      } catch (error) {
        return errorResponse(error);
      }
    }
  • The registration of the get_company_profile tool.
    // Company Profile
    server.registerTool(
      'get_company_profile',
      {
        description: 'Get detailed company profile information including description, industry, sector, CEO, and more',
        inputSchema: CompanyProfileSchema,
      },
      async (args: z.infer<typeof CompanyProfileSchema>) => {
        try {
          const data = await fetchFMP<CompanyProfile[]>(`/profile?symbol=${args.symbol.toUpperCase()}`);
          return jsonResponse(data);
        } catch (error) {
          return errorResponse(error);
        }
      }
    );
  • The Zod schema definition for the get_company_profile tool input.
    const CompanyProfileSchema = z.object({
      symbol: SymbolSchema.describe('Stock ticker symbol'),
    });
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 retrieves information ('Get'), implying a read-only operation, but does not address other behavioral aspects such as rate limits, authentication needs, error handling, or data freshness. 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 action and provides relevant examples without unnecessary details. Every word earns its place, making it highly concise and well-structured.

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's moderate complexity (single parameter, no output schema, no annotations), the description is minimally adequate. It clarifies the tool's purpose but lacks behavioral details and usage guidelines. Without an output schema, it does not explain return values, though the examples hint at data types. It meets basic needs but has clear gaps.

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 input schema has 100% description coverage, with the single parameter 'symbol' documented as 'Stock ticker symbol'. The description does not add any meaning beyond this, such as format examples or constraints, but the schema adequately covers the parameter, meeting the baseline for high schema coverage.

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 ('Get') and resource ('detailed company profile information'), and lists example fields like description, industry, sector, and CEO. However, it does not explicitly differentiate from siblings like get_quote or get_key_metrics, which might provide overlapping or related data, keeping it from 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. With many sibling tools available (e.g., get_quote for price data, get_key_metrics for financial metrics), there is no indication of context, prerequisites, or exclusions, leaving the agent to infer usage based on tool names alone.

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