Skip to main content
Glama
MCP-100

Stock Market MCP Server

by MCP-100

get_market_report

Generate US stock market reports and briefings to analyze financial data and track market performance.

Instructions

Generate US market report/briefing

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the get_market_report tool. It fetches the market status from the Alpha Vantage API (MARKET_STATUS function) using the pre-configured axios instance and returns the raw JSON response as a text content block.
    private async handleGetMarketReport() {
      const response = await this.axiosInstance.get('', {
        params: {
          function: 'MARKET_STATUS'
        }
      });
    
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(response.data, null, 2)
        }]
      };
    }
  • src/index.ts:67-74 (registration)
    Registration of the get_market_report tool in the ListToolsRequestSchema response. Defines name, description ('Generate US market report/briefing'), and inputSchema (empty object with no properties or required fields).
    {
      name: 'get_market_report',
      description: 'Generate US market report/briefing',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
  • src/index.ts:116-117 (registration)
    Dispatch logic in the CallToolRequestSchema handler: switch case for 'get_market_report' that invokes this.handleGetMarketReport().
    case 'get_market_report':
      return await this.handleGetMarketReport();
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 'generates' a report, implying a read-only operation, but doesn't clarify if it requires authentication, has rate limits, returns structured or unstructured data, or any other behavioral traits. The description is too minimal for a tool with no annotation support.

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 fluff. It's appropriately sized for a zero-parameter tool and front-loads the essential information.

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 doesn't explain what the generated report contains, its format, or any behavioral context. For a tool that 'generates' something, more detail is needed to help the agent understand what to expect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100%, so there's no need for parameter documentation in the description. The baseline for this scenario is 4, as the description appropriately doesn't waste space on non-existent parameters.

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 ('Generate') and resource ('US market report/briefing'), making it immediately understandable. It doesn't explicitly differentiate from sibling tools like 'get_company_overview' or 'get_financial_statement', but the scope ('US market') provides some implicit distinction.

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 'get_company_overview' or 'get_financial_statement'. It doesn't mention any prerequisites, exclusions, or specific contexts for usage, leaving the agent to infer 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