Skip to main content
Glama

EODHD (Unofficial)

Eodhd Fundamentals

eodhd_fundamentals
Read-onlyIdempotent

Get fundamentals + analyst price target & estimates for , company profile, highlights, valuation ratios, analyst ratings/target price, and forward EPS/revenue estimates. Symbol uses EXCHANGE.SUFFIX format, e.g. "AAPL.US". Example: eodhd_fundamentals({ symbol: "AAPL.US", _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_fundamentals"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesTicker with exchange suffix, e.g. "AAPL.US", "TSLA.US", "BMW.XETRA"
_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",
      +    "symbol": "BMW.XETRA"
      +  }
      +]
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds that it is a token-authenticated third-party call returning analyst estimates, but says nothing about call cost, rate limits, or freshness of estimates. With annotations carrying the behavioral load, a 3 is appropriate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The first sentence is a dense comma-list of return fields that is hard to parse, and the invocation example partially repeats the schema's own examples array. It is front-loaded and reasonably short, but the run-on enumeration costs clarity.

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

Completeness3/5

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

For a simple two-parameter read with a fully documented schema, the description covers what is returned and the ticker format. It lacks any indication of auth failure behavior, rate-limit consequences (the schema mentions 20 calls/day), or how missing fundamentals are surfaced, which matter for an external API call with no output schema.

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 coverage is 100%, so the baseline is 3, but the description reinforces the EXCHANGE.SUFFIX ticker format with a concrete example ('AAPL.US'), which is the one parameter most likely to be misformatted. It adds little on _apiKey beyond what the schema says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Get fundamentals + analyst price target & estimates') and enumerates the returned data blocks (company profile, highlights, valuation ratios, analyst ratings, forward EPS/revenue estimates). It is not a tautology of the title. It does not differentiate itself from siblings like company_facts or entity_profile, so it stops short of a 5.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given, and no alternatives are named. An agent cannot tell from the description whether this overlaps with company_facts or entity_profile. Usage is only implied by the data it returns.

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.