Skip to main content
Glama

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.

Input Schema

TableJSON 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.
tickerNoThe stock ticker symbol (e.g. AAPL, MSFT).
end_dateNoThe end date for the price data (format: YYYY-MM-DD). Provider reference (supplier schema): `{"format":"date","type":"string"}`.
intervalNoThe time interval for the price data. Provider reference (supplier schema): `{"enum":["day","week","month","year"],"type":"string"}`.
start_dateNoThe start date for the price data (format: YYYY-MM-DD). Provider reference (supplier schema): `{"format":"date","type":"string"}`.
interval_multiplierNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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)."
  2. 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: +[]
  3. First observed

TDQS

B3.1/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, covering the safety profile. The description adds the useful EOD/historical granularity but says nothing about pagination via cursor, default interval behavior, or what happens when no ticker is supplied.

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?

One front-loaded sentence stating the core purpose, plus a clearly delimited pricing block. Nothing is wasted, though the pricing boilerplate dominates the visible text relative to the useful content.

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?

The tool has 6 parameters, zero required, and an output schema, yet the description gives no default semantics (default interval, behavior with no ticker, cursor pagination flow). An agent cannot tell from the description how to invoke it correctly with an empty argument set.

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 cursor, ticker, dates, and interval, and the description adds nothing param-specific. Baseline 3 applies since the schema carries the load.

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?

States a specific verb and resource ('Get end-of-day (EOD) historical price data for stocks'), which is clear. However, it never names or contrasts with the obvious sibling get_financial_prices_snapshot, leaving the historical-vs-snapshot distinction to inference.

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 on when to use this tool versus alternatives such as get_financial_prices_snapshot or batch_quote. The word 'historical' implies usage but no explicit context or exclusions are given.

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