Skip to main content
Glama

EODHD (Unofficial)

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

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "AAPL.US",
      "_apiKey": "your-eodhd-api-key"
    },
    "name": "eodhd_eod_prices"
  }
}

Input 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

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the symbol format requirement and period sampling semantics, but does not mention rate limits or pagination behavior (the free-tier limit lives only in the schema).

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?

Front-loads the core purpose, then the format constraint, then optional parameters, then a concrete example. Efficient overall, though the example partially duplicates the schema's examples array.

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?

No output schema exists, and the description compensates by naming the returned fields (OHLCV plus adjusted close). Combined with full schema coverage and annotations, an agent has enough to call it correctly; only rate-limit and pagination details are absent.

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 the baseline is 3. The description reinforces the EXCHANGE.SUFFIX symbol format and the YYYY-MM-DD date format and shows a full example call, but adds little beyond what the schema already documents.

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 verb and resource ("Get historical daily prices") and names the returned fields (end-of-day OHLCV plus adjusted close). The scope is distinct from the only close sibling, eodhd_fundamentals, so an agent can tell them apart without opening either 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?

Explains the optional bounding via from/to and period, which implies how to narrow a query, but gives no explicit when-to-use or when-not-to-use guidance relative to alternatives. Usage is implied 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.