Skip to main content
Glama

fetch_time_series_daily

[Personal research only] Fetch daily stock data with OHLCV (Open, High, Low, Close, Volume) information for each trading day.

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": {
      "symbol": "<symbol>"
    },
    "name": "fetch_time_series_daily"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesStock ticker symbol (e.g., 'AAPL', 'MSFT', 'TSLA') for which to retrieve daily data
datatypeNoResponse data type.json
end_dateNoOptional end date filter in YYYY-MM-DD format (inclusive).
outputsizeNoData output size.compact
start_dateNoOptional start date filter in YYYY-MM-DD format (inclusive).
max_data_pointsNoMaximum number of time series data points to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It does disclose the returned record shape (OHLCV per trading day) and flags a restricted use scope, which is real value. However, it says nothing about auth requirements, rate limits, pagination/truncation behavior, or how outputsize interacts with max_data_points — significant omissions for a 6-parameter data-fetch tool.

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?

A single efficient sentence with no padding, and the resource and payload are front-loaded. The bracketed personal-research prefix is slightly awkward but does not bury the core statement.

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?

The 100%-covered schema and the explicit OHLCV return description cover the essentials, and no output schema means return values need not be explained. Still, with no annotations and six parameters, a caller would benefit from knowing how start_date/end_date, outputsize, and max_data_points interact — none of which is addressed.

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 100%, so all six parameters are already documented in the schema, making 3 the baseline. The description adds only 'each trading day' granularity and the OHLCV field meanings; it does not clarify the opaque values such as 'compact' vs. full outputsize or how max_data_points truncates the range.

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 — fetch daily stock data — and specifies the payload (OHLCV per trading day), which distinguishes it from fetch_quote and the technical-indicator siblings. It does not explicitly name the monthly/weekly siblings it competes with, so the differentiation is implied by the word 'daily' rather than spelled out.

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 when-to-use statement, no exclusions, and no reference to fetch_time_series_weekly, fetch_time_series_monthly, or fetch_quote as alternatives. The bracketed '[Personal research only]' is a scope/licensing caveat, not guidance on when to select this tool over a sibling.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources