Skip to main content
Glama

Eodhd

by io.github.pipeworx-io
OverviewDiscussionsAdmin

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

Input Schema

TableJSON 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

A3.8/5.0
Behavior3/5

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

Annotations already provide readOnlyHint and idempotentHint. Description adds list of returned data categories but does not mention rate limits or external API dependency beyond parameter description.

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; efficient, front-loaded with main purpose, no fluff.

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?

For a tool with two clear parameters and rich annotations, description adequately lists output categories and provides example. Without output schema, could be more explicit about return structure.

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 coverage is 100% with detailed parameter descriptions. Tool description repeats symbol format and example, adding minimal new semantic meaning.

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?

The description clearly states it retrieves fundamentals, analyst estimates, and company data. It specifies symbol format with exchange suffix, differentiating from likely sibling eodhd_eod_prices which provides price data.

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?

Provides an example and symbol format but no explicit guidance on when to use vs alternatives like eodhd_eod_prices. Usage context is implied but not contrasted.

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