Skip to main content
Glama
Sign In

AIsa Finance

by one.aisa
OverviewDiscussionsAdmin

Get Historical Stock Prices

get_financial_prices
Read-onlyIdempotent

Get end-of-day (EOD) historical price data for stocks.

Published reference price: $0.02 USD per successful request. Account-specific pricing and final settlement may differ.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "end_date": "<end_date>",
      "interval": "<interval>",
      "start_date": "<start_date>",
      "ticker": "<ticker>"
    },
    "name": "get_financial_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoOpaque pagination cursor from a previous response's next_page_url. When provided, all other query parameters are ignored: the cursor carries the original request's filters. Treat it as opaque; do not construct or modify it.
tickerYesThe stock ticker symbol (e.g. AAPL, MSFT).
end_dateYesThe end date for the price data (format: YYYY-MM-DD). Provider reference (supplier schema): `{"format":"date","type":"string"}`.
intervalYesThe time interval for the price data. Provider reference (supplier schema): `{"enum":["day","week","month","year"],"type":"string"}`.
start_dateYesThe start date for the price data (format: YYYY-MM-DD). Provider reference (supplier schema): `{"format":"date","type":"string"}`.
interval_multiplierNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[]New value: +[
+  "end_date",
+  "interval",
+  "start_date",
+  "ticker"
+]
  2. Changed5 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Opaque pagination cursor from a previous response's next_page_url. When provided, all other query parameters are ignored: the cursor carries the original request's filters. Treat it as opaque; do not construct or modify it.",
+  "type": "string"
+}
    • addedInput schema / properties / end_date / description
      Added value: +"The end date for the price data (format: YYYY-MM-DD).\n\nProvider reference (supplier schema): `{\"format\":\"date\",\"type\":\"string\"}`."
    • addedInput schema / properties / interval / description
      Added value: +"The time interval for the price data.\n\nProvider reference (supplier schema): `{\"enum\":[\"day\",\"week\",\"month\",\"year\"],\"type\":\"string\"}`."
    • addedInput schema / properties / start_date / description
      Added value: +"The start date for the price data (format: YYYY-MM-DD).\n\nProvider reference (supplier schema): `{\"format\":\"date\",\"type\":\"string\"}`."
    • addedInput schema / properties / ticker / description
      Added value: +"The stock ticker symbol (e.g. AAPL, MSFT)."
  3. Changed9 schema fields changed
    • removedInput schema / properties / end_date / description
      Removed value: -"The end date for the price data (format: YYYY-MM-DD)."
    • removedInput schema / properties / end_date / format
      Removed value: -"date"
    • removedInput schema / properties / interval / description
      Removed value: -"The time interval for the price data."
    • removedInput schema / properties / interval / enum
      Removed value: -[
-  "day",
-  "week",
-  "month",
-  "year"
-]
    • addedInput schema / properties / interval_multiplier
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / start_date / description
      Removed value: -"The start date for the price data (format: YYYY-MM-DD)."
    • removedInput schema / properties / start_date / format
      Removed value: -"date"
    • removedInput schema / properties / ticker / description
      Removed value: -"The stock ticker symbol (e.g. AAPL, MSFT)."
    • changedInput schema / required
      Previous value: -[
-  "ticker",
-  "interval",
-  "start_date",
-  "end_date"
-]New value: +[]
  4. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact, the $0.02 per successful request publishing price, but says nothing about pagination behavior (the cursor path), rate limits, or whether prices are split/dividend adjusted.

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 substantive content is a single front-loaded sentence with zero waste. The pricing block is boilerplate wrapped in HTML comment markers, which is minor clutter but at least short.

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?

An output schema exists, so return-value shapes need not be described, and annotations carry the safety profile. Still missing for a six-parameter, cursor-paginated historical-series tool: the snapshot-vs-historical routing rule and any note on price adjustment conventions or timezone of the date range.

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 description coverage is 83%, so the schema already documents ticker, start_date, end_date, interval and cursor thoroughly. The description adds no parameter-level detail beyond 'end-of-day', and the one undocumented field (interval_multiplier) is left unexplained in both places.

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 states a specific verb and resource: get end-of-day historical price data for stocks. The word 'historical' implicitly separates it from the sibling get_financial_prices_snapshot, but that sibling is never named, so the agent must infer the 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?

There is no statement of when to use this tool versus get_financial_prices_snapshot or the many other financial siblings, and no prerequisites or exclusions. The only hint is the adjective 'historical', which the agent gets from the name anyway.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AIsa Finance toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources