Skip to main content
Glama
Sign In

spicytrade

by io.github.ferdousbhai
OverviewDiscussionsAdmin

read_price_history

Read-only

Dividend-adjusted Yahoo history with optional local SMA, EMA, RSI, MACD, or Bollinger studies; not a current quote. A study series carries only the values it has. Each series values[i] is the study value for the bar at prices.date[firstPriceIndex + i]; earlier bars are warm-up and have no value.

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": "read_price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost recent rows to return. Defaults to 120.
symbolYes
endDateNoInclusive end date in YYYY-MM-DD form. Defaults to today.
studiesNoOptional studies from adjusted closes; kind is SMA, EMA, RSI, BBANDS or MACD, uppercase. Defaults: period 14; MACD 12/26/9; Bollinger deviations 2.
intervalNoDaily by default.
startDateNoStart date in YYYY-MM-DD form. Defaults to one year before endDate. The inclusive range spans at most 4000 calendar days, whatever the interval.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real behavioral facts the annotations cannot: values are dividend-adjusted, study series are sparse ('carry only the values it has'), and warm-up bars return no value. It stops short of stating pagination or upstream failure 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?

Three sentences, front-loaded with purpose first, then return-shape semantics. Dense and mostly earning its place, though the indexing sentence is notation-heavy and could be tightened for readability.

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?

With no output schema, the description must explain the return shape and does so via the alignment and warm-up rules, which is the key ambiguity for a study-augmented time series. It leaves some uncertainty about the container fields (prices, firstPriceIndex) that the description references without introducing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is already 83%, so the schema carries most parameter meaning. The description still contributes the index-alignment rule (values[i] maps to prices.date[firstPriceIndex + i]) and the warm-up caveat, which is genuine added semantics rather than repetition.

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?

States a specific resource (dividend-adjusted price history) plus the optional study overlay, and explicitly scopes out the sibling case with 'not a current quote', so an agent can separate it from read_instrument_quotes without opening the schema.

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 phrase 'not a current quote' implicitly routes live-quote needs to another tool, but there is no explicit when-to-use/when-not statement and no named alternative among read_instrument_quotes or read_market_metrics. 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.

All spicytrade 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