Skip to main content
Glama
imbenrabi

Financial Modeling Prep MCP Server

getDividendAdjustedChart

Read-onlyIdempotent

Retrieve dividend-adjusted price and volume data for any stock over a date range to analyze performance with dividend distributions accounted for.

Instructions

Analyze stock performance with dividend adjustments using the FMP Dividend-Adjusted Price Chart API. Access end-of-day price and volume data that accounts for dividend payouts, offering a more comprehensive view of stock trends over time.

Input Schema

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

Implementation Reference

  • Registration of the 'getDividendAdjustedChart' tool on the MCP server with its schema (symbol, from_date, to) and handler callback.
    server.tool(
      "getDividendAdjustedChart",
      "Analyze stock performance with dividend adjustments using the FMP Dividend-Adjusted Price Chart API. Access end-of-day price and volume data that accounts for dividend payouts, offering a more comprehensive view of stock trends over time.",
      {
        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.getDividendAdjustedChart(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,
          };
        }
      }
    );
  • Handler function for getDividendAdjustedChart - destructures the input, calls chartClient.getDividendAdjustedChart, and returns the result as JSON text content.
    async ({ symbol, from_date: from, to }) => {
      try {
        const results = await chartClient.getDividendAdjustedChart(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,
        };
      }
    }
  • Input schema for the tool defining three parameters: symbol (required string), from_date (optional string), to (optional string).
    {
      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)"),
    },
  • ChartClient.getDividendAdjustedChart API method that makes the actual HTTP GET request to '/historical-price-eod/dividend-adjusted' endpoint with symbol, from, to parameters.
    async getDividendAdjustedChart(
      symbol: string,
      from?: string,
      to?: string,
      options?: {
        signal?: AbortSignal;
        context?: FMPContext;
      }
    ): Promise<UnadjustedChartData[]> {
      return super.get<UnadjustedChartData[]>(
        "/historical-price-eod/dividend-adjusted",
        { symbol, from, to },
        options
      );
    }
  • Type definition for UnadjustedChartData - the data shape returned by getDividendAdjustedChart (symbol, date, adjOpen, adjHigh, adjLow, adjClose, volume).
    export interface UnadjustedChartData {
      symbol: string;
      date: string;
      adjOpen: number;
      adjHigh: number;
      adjLow: number;
      adjClose: number
      volume: number;
    }
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint. The description adds context about dividend adjustments and end-of-day data but does not reveal further behavioral traits (e.g., rate limits, data granularity). It does not contradict 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 two sentences, front-loading the purpose and key benefit. Every sentence adds value without verbosity.

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, and the description only mentions 'price and volume data' without specifying the response structure or fields. For a data retrieval tool, this is an adequate but not complete specification.

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?

Schema coverage is 100% with clear descriptions for symbol, from_date, and to. The description adds no additional meaning beyond what the schema provides, so baseline score of 3 is appropriate.

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 specifies the tool retrieves dividend-adjusted end-of-day price and volume data for stock performance analysis. It distinguishes itself from siblings like getUnadjustedChart by explicitly mentioning dividend adjustments.

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 for dividend-adjusted trend analysis but does not explicitly state when to prefer this over alternatives like getUnadjustedChart, getFullChart, or getLightChart. No exclusions or alternative recommendations are 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