Skip to main content
Glama
imbenrabi

Financial Modeling Prep MCP Server

getUnadjustedChart

Read-onlyIdempotent

Retrieve stock price and volume data without split adjustments for any symbol and date range. Get open, high, low, close prices and volume for accurate performance insights.

Instructions

Access stock price and volume data without adjustments for stock splits with the FMP Unadjusted Stock Price Chart API. Get accurate insights into stock performance, including open, high, low, and close prices, along with trading volume, without split-related changes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesStock symbol
from_dateNoStart date (YYYY-MM-DD)
toNoEnd date (YYYY-MM-DD)

Implementation Reference

  • MCP tool handler for 'getUnadjustedChart' — defines the tool schema (symbol, from_date, to) and handler function that calls chartClient.getUnadjustedChart
    server.tool(
      "getUnadjustedChart",
      "Access stock price and volume data without adjustments for stock splits with the FMP Unadjusted Stock Price Chart API. Get accurate insights into stock performance, including open, high, low, and close prices, along with trading volume, without split-related changes.",
      {
        symbol: z.string().describe("Stock symbol"),
        from_date: z.string().optional().describe("Start date (YYYY-MM-DD)"),
        to: z.string().optional().describe("End date (YYYY-MM-DD)"),
      },
      async ({ symbol, from_date: from, to }) => {
        try {
          const results = await chartClient.getUnadjustedChart(symbol, from, to);
          return {
            content: [{ type: "text", text: JSON.stringify(results, null, 2) }],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error: ${
                  error instanceof Error ? error.message : String(error)
                }`,
              },
            ],
            isError: true,
          };
        }
      }
    );
  • Type definition for the unadjusted chart data returned by the API
    export interface UnadjustedChartData {
      symbol: string;
      date: string;
      adjOpen: number;
      adjHigh: number;
      adjLow: number;
      adjClose: number
      volume: number;
    }
  • Registration of the chart module (including getUnadjustedChart) in the core module adapters registry
      chart: createModuleAdapter('chart', registerChartTools),
      company: createModuleAdapter('company', registerCompanyTools),
      cot: createModuleAdapter('cot', registerCOTTools),
      esg: createModuleAdapter('esg', registerESGTools),
      economics: createModuleAdapter('economics', registerEconomicsTools),
      dcf: createModuleAdapter('dcf', registerDCFTools),
    };
  • ChartClient.getUnadjustedChart — API client method that fetches unadjusted chart data from the /historical-price-eod/non-split-adjusted endpoint
    async getUnadjustedChart(
      symbol: string,
      from?: string,
      to?: string,
      options?: {
        signal?: AbortSignal;
        context?: FMPContext;
      }
    ): Promise<UnadjustedChartData[]> {
      return super.get<UnadjustedChartData[]>(
        "/historical-price-eod/non-split-adjusted",
        { symbol, from, to },
        options
      );
    }
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true. The description adds that the tool returns open, high, low, close prices and volume, which is helpful but minimal beyond annotations. No mention of side effects, auth needs, or rate limits.

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

Conciseness4/5

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

The description is two sentences, front-loading the main purpose. It is efficient with no fluff, though slightly verbose with repetitive 'without split-related changes'. Could be tighter but effectively concise.

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?

No output schema exists, so description must explain return data. It mentions OHLCV and volume, which is adequate for a chart tool. However, it lacks details on date range behavior (e.g., pagination, limits) and does not clarify that from_date and to are optional. Adequate but not complete.

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?

Input schema has 100% coverage with descriptions for all three parameters (symbol, from_date, to). The description repeats the unadjusted nature but adds no new meaning or format details beyond the schema. Baseline 3 is appropriate as description does not compensate.

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 tool retrieves unadjusted stock price data, specifically 'without adjustments for stock splits,' and mentions the API source. It uses specific verbs ('access') and resource ('Unadjusted Stock Price Chart'), effectively distinguishing it from adjusted chart tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use when unadjusted data is needed, but lacks explicit guidance on when not to use or alternatives (e.g., 'Use this for raw data; for adjusted data use getDividendAdjustedChart'). No exclusions or context provided.

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/imbenrabi/Financial-Modeling-Prep-MCP-Server'

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