Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_finance_download

Fetch batch historical Yahoo Finance prices for up to 25 symbols in one POST, with OHLCV data, dividends, splits, and capital gains.

Instructions

Yahoo Finance batch historical prices. Returns historical prices for up to 25 symbols in one POST. The body requires symbols; period, start, end, interval, include_prepost and include_actions are optional. Each result is one symbol, with price points (open, high, low, close, adjusted close, volume) and dividend, split and capital-gain events, or an error for that symbol.

Input Schema

NameRequiredDescriptionDefault
requestYesBatch download request

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / request / properties
      Added value: +{
+  "auto_adjust": {
+    "type": "boolean"
+  },
+  "back_adjust": {
+    "type": "boolean"
+  },
+  "end": {
+    "type": "string"
+  },
+  "include_actions": {
+    "type": "boolean"
+  },
+  "include_prepost": {
+    "type": "boolean"
+  },
+  "interval": {
+    "type": "string"
+  },
+  "keepna": {
+    "type": "boolean"
+  },
+  "period": {
+    "type": "string"
+  },
+  "rounding": {
+    "type": "boolean"
+  },
+  "start": {
+    "type": "string"
+  },
+  "symbols": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+}
    • addedInput schema / properties / request / required
      Added value: +[
+  "symbols"
+]
  2. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and discloses important behavior: one POST, max 25 symbols, per-symbol results, price fields, corporate-action events, and per-symbol errors. It does not mention authentication or rate limits, but covers the main output and 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the tool's purpose and batch limit, then covers required inputs, optional inputs, and expected output. Every sentence adds relevant information with no boilerplate.

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?

Given the nested request object and absence of an output schema, the description explains the return structure, corporate-action events, and per-symbol error handling. It is mostly complete, though it does not account for every optional parameter in the nested schema.

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 high, so the schema already provides the baseline parameter documentation. The description adds useful context by naming the required `symbols` field and several optional fields, but it omits `keepna`, `rounding`, `auto_adjust`, and `back_adjust` and gives no format examples for dates or intervals.

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 and operation: Yahoo Finance batch historical prices, up to 25 symbols in one POST. The batch scope distinguishes it from single-symbol siblings like yahoo_finance_ticker_history without needing to open 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 batch nature and 25-symbol limit imply when to use it, but the description does not explicitly name alternatives such as yahoo_finance_ticker_history or state when not to use this tool. Usage is therefore inferable but not spelled out.

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

Deploy Server

Other Tools