Skip to main content
Glama

Eodhd

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Eodhd Eod Prices

eodhd_eod_prices
Read-onlyIdempotent

Get historical daily prices for — end-of-day OHLCV plus adjusted close. Symbol uses EXCHANGE.SUFFIX format, e.g. "AAPL.US". Optionally bound with from/to (YYYY-MM-DD) and period (d/w/m). Example: eodhd_eod_prices({ symbol: "AAPL.US", from: "2024-01-01", to: "2024-06-30", _apiKey: "your-api_token" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoEnd date in YYYY-MM-DD format (optional)
fromNoStart date in YYYY-MM-DD format (optional)
periodNoSampling period: "d" daily (default), "w" weekly, "m" monthly
symbolYesTicker with exchange suffix, e.g. "AAPL.US"
_apiKeyYesEODHD api_token (get one free at eodhd.com; free tier 20 calls/day)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-eodhd-api-key",
+    "symbol": "AAPL.US"
+  },
+  {
+    "_apiKey": "your-eodhd-api-key",
+    "from": "2024-01-01",
+    "period": "d",
+    "symbol": "TSLA.US",
+    "to": "2024-06-30"
+  }
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, safe, idempotent. Description adds return data OHLCV+adjusted close, date range, and period options, which are beyond annotations.

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?

Two sentences plus example; no superfluous content. Efficiently conveys core purpose and usage.

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?

Covers purpose, parameters, example, and return type. Lacks pagination or rate limit info, but schema provides API key limits. Sufficient for a simple data retrieval tool.

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 describes all parameters (100% coverage). Description adds a concrete example and symbol format explanation, providing extra clarity beyond schema.

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?

Clearly states it gets historical daily prices (OHLCV plus adjusted close) for a symbol in EXCHANGE.SUFFIX format. Distinguishes from sibling eodhd_fundamentals.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides context for when to use (get historical prices) and symbol format, but lacks explicit when-not-to-use or alternative tool guidance.

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

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