Skip to main content
Glama

fetch_time_series_monthly

[Personal research only] Fetch monthly stock data with OHLCV (Open, High, Low, Close, Volume) aggregated by month.

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_monthly"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesStock ticker symbol (e.g., 'AAPL', 'MSFT', 'TSLA') for which to retrieve monthly data
datatypeNoResponse data type.json
end_dateNoOptional end date filter in YYYY-MM-DD format (inclusive).
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

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the returned data shape (OHLCV) and monthly aggregation, plus a 'Personal research only' restriction, but it does not mention rate limits, authentication, output formatting, or truncation behavior.

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 definition is compact and front-loaded in a single sentence. The bracketed 'Personal research only' tag is of unclear value for invocation, but the core description is efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only fetch tool with fully documented parameters and no output schema, the description is mostly complete: it identifies the data returned and the monthly aggregation. Minor gaps remain around output format and explicit sibling routing.

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 five parameters are already documented in the schema. The description does not add parameter-specific meaning beyond the schema baseline.

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 states a specific verb and resource: fetch monthly stock data with OHLCV aggregated by month. The monthly aggregation clearly distinguishes it from sibling tools like fetch_time_series_daily and fetch_time_series_weekly.

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 monthly scope implies when this tool is appropriate versus daily or weekly siblings, but the description does not explicitly say 'use this for monthly data' or name alternatives. Usage is inferable rather than stated.

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