Skip to main content
Glama
deepsuthar496

Alpha Vantage MCP Server

get_company_overview

Retrieve company information and key financial metrics for any stock symbol to analyze business fundamentals and performance data.

Instructions

Get company information and key metrics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesThe stock symbol (e.g., AAPL)

Implementation Reference

  • The core handler function for the 'get_company_overview' tool. It makes an API request to Alpha Vantage's OVERVIEW function using the provided stock symbol and returns the response data as formatted JSON text.
    private async getCompanyOverview(args: any) {
      const response = await this.axiosInstance.get('', {
        params: {
          function: 'OVERVIEW',
          symbol: args.symbol,
        },
      });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • src/index.ts:107-120 (registration)
    Registers the 'get_company_overview' tool in the MCP server's list of tools, providing its name, description, and input schema.
    {
      name: 'get_company_overview',
      description: 'Get company information and key metrics',
      inputSchema: {
        type: 'object',
        properties: {
          symbol: {
            type: 'string',
            description: 'The stock symbol (e.g., AAPL)',
          },
        },
        required: ['symbol'],
      },
    },
  • Defines the input schema for the 'get_company_overview' tool, requiring a 'symbol' string parameter.
    inputSchema: {
      type: 'object',
      properties: {
        symbol: {
          type: 'string',
          description: 'The stock symbol (e.g., AAPL)',
        },
      },
      required: ['symbol'],
    },
  • Dispatches the tool call to the specific getCompanyOverview handler method within the main CallToolRequestSchema handler.
    case 'get_company_overview':
      return await this.getCompanyOverview(request.params.arguments);
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 'Get[s] company information and key metrics,' implying a read-only operation, but doesn't disclose any behavioral traits like rate limits, authentication needs, or what specific metrics are returned. This is a significant gap for a tool with no annotations.

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 with no wasted words, making it appropriately sized and front-loaded. It directly states the tool's purpose without unnecessary elaboration.

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 complexity (financial data retrieval), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what 'company information and key metrics' includes, how results are formatted, or any limitations, leaving gaps for an AI agent to understand the tool fully.

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 'symbol' parameter clearly documented. The description doesn't add any meaning beyond what the schema provides, such as examples or constraints, so it meets the baseline score of 3 for high schema coverage without extra value.

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 ('company information and key metrics'), making it understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_stock_price' or 'get_daily_time_series', which might provide overlapping or related financial data, so it falls short of 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 any context, exclusions, or comparisons to sibling tools such as 'get_stock_price' or 'get_technical_indicator', leaving the agent without clear usage instructions.

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/deepsuthar496/alpha-ventage-mcp'

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