Skip to main content
Glama

stocks_get_chart

Retrieve historical price data for a stock to analyze past performance and trends.

Instructions

Get historical price data for a stock

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:83-83 (registration)
    Tool registration entry in the TOOLS array with name 'stocks_get_chart' and description 'Get historical price data for a stock'. This is a stub/inspection server where all tools return a placeholder message.
    ["stocks_get_chart", "Get historical price data for a stock"],
  • The handler for all tools (including stocks_get_chart). It's a generic stub handler that returns a placeholder message instructing the user to install the real local-mcp binary. The real implementation is in a native binary not present in this codebase.
    server.tool(name, desc, {}, async () => ({
      content: [{ type: "text", text: "This is an inspection stub. Install Local MCP: npx -y local-mcp@latest setup" }],
    }));
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must disclose behavior. It only says 'historical price data', but omits details like supported time ranges, data frequency (e.g., daily, hourly), or what fields (open, close, high, low, volume) are returned. This is insufficient for an agent to anticipate output.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (5 words), but sacrifices necessary details. It is front-loaded but incomplete, making it barely adequate.

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

Completeness1/5

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

Given the complexity of historical stock data and no annotations or output schema, the description is severely incomplete. It fails to specify how to input the stock symbol or date range, leaving the agent unable to correctly invoke the tool.

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?

Although there are zero parameters (baseline 4), the description does not explain how the stock is identified—likely requiring prior context or implicit state. The description adds some meaning ('historical price data') but fails to clarify the lack of parameters, leaving ambiguity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get' and the resource 'historical price data for a stock'. It distinguishes from sibling tools like 'stocks_get_quote' (current quote) and 'stocks_search_symbol' (search symbols), making its purpose unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it does not explain that 'stocks_get_quote' should be used for real-time data, or how to specify the stock symbol or date range.

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/lanchuske/local-mcp-releases'

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