Skip to main content
Glama
MCP-100

Stock Market MCP Server

by MCP-100

get_company_overview

Retrieve company overview and key financial metrics by entering a stock ticker symbol to analyze investment opportunities.

Instructions

Get company overview and key metrics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesStock ticker symbol

Implementation Reference

  • The handler function that executes the tool logic: fetches company overview data from Alpha Vantage API using the 'OVERVIEW' endpoint and returns the JSON response.
    private async handleGetCompanyOverview(args: { symbol: string }) {
      const response = await this.axiosInstance.get('', {
        params: {
          function: 'OVERVIEW',
          symbol: args.symbol
        }
      });
    
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(response.data, null, 2)
        }]
      };
    }
  • Input schema definition for the get_company_overview tool, specifying the required 'symbol' parameter.
    inputSchema: {
      type: 'object',
      properties: {
        symbol: {
          type: 'string',
          description: 'Stock ticker symbol'
        }
      },
      required: ['symbol']
    }
  • src/index.ts:94-107 (registration)
    Tool registration in the ListTools response, including name, description, and schema.
    {
      name: 'get_company_overview',
      description: 'Get company overview and key metrics',
      inputSchema: {
        type: 'object',
        properties: {
          symbol: {
            type: 'string',
            description: 'Stock ticker symbol'
          }
        },
        required: ['symbol']
      }
    }
  • src/index.ts:125-131 (registration)
    Dispatch/registration logic in CallToolRequest handler that validates input and calls the tool handler.
    case 'get_company_overview': {
      if (!request.params.arguments || typeof request.params.arguments !== 'object') {
        throw new McpError(ErrorCode.InvalidParams, 'Invalid arguments');
      }
      const args = request.params.arguments as { symbol: string };
      return await this.handleGetCompanyOverview(args);
    }
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 only states what the tool does ('Get company overview and key metrics') without mentioning any behavioral traits such as read-only status, potential rate limits, authentication needs, or what the output might look like. 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 directly states the tool's purpose without any wasted words. It is appropriately sized and front-loaded, making it easy to parse quickly.

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 lack of annotations and output schema, the description is incomplete. It does not explain what 'company overview and key metrics' includes, how the data is returned, or any behavioral aspects like error handling. For a tool with no structured data beyond the input schema, this leaves significant gaps in understanding.

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 as 'Stock ticker symbol'. The description does not add any additional meaning beyond this, such as format examples or constraints, so it meets the baseline score of 3 where the schema does the heavy lifting.

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 overview and key metrics'), making it easy to understand what it does. However, it doesn't distinguish itself from sibling tools like 'get_financial_statement' or 'get_market_report', which might also provide company-related data, so it doesn't reach the highest 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 like the sibling tools. It lacks explicit instructions on 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/MCP-100/stock-market-server'

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