Skip to main content
Glama

Eodhd

by io.github.pipeworx-io

Recall

recall
Read-onlyIdempotent

Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoMemory key to retrieve (omit to list all keys)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive. Description adds scoping (anonymous IP, key hash, account ID) and listing behavior. Good complement.

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-loaded with main action, efficient sentences. Slightly verbose with pairing mention, but overall concise.

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

Completeness5/5

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

For a simple read tool, description covers usage, scoping, and pairing. No output schema, but return behavior is implied. Complete.

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 100%, baseline 3. Description restates schema detail (omit key to list) but doesn't add new parameter-level meaning beyond that.

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?

Clear verb 'retrieve' with specific resource 'a value previously saved via remember' or 'list all saved keys'. Distinguishes from siblings by naming 'remember' and 'forget' explicitly.

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?

Explains use case (look up stored context without re-deriving) and scope (by identifier). Could note when not to use, but it's straightforward.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation2/5

Multiple tool clusters overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route research questions; polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, and bet_research all hunt prediction-market edges; ai_visibility_check and scan_competitor_ai_presence do nearly the same job. The verbose descriptions help, but an agent would still struggle to pick the right tool in these clusters.

Naming Consistency2/5

Everything is snake_case, but there is no coherent pattern: some names are verb_noun (compare_entities, validate_claim), some are bare verbs (remember, forget, recall), some are prefixed by domain (eodhd_*, pipeworx_*, polymarket_*, ai_visibility_*), and the Eodhd prefix clashes with the Pipeworx family. The conventions feel inherited from multiple unrelated codebases rather than a unified design.

Tool Count2/5

33 tools is already heavy for most servers, but the real problem is that only 2 tools (eodhd_eod_prices, eodhd_fundamentals) relate to the server's stated purpose. The other 31 span Pipeworx research, Polymarket betting, memory, subscriptions, feedback, llms.txt generation, and npm dependency checking — a massively over-scoped grab bag for a server named 'Eodhd'.

Completeness2/5

For the nominal EODHD domain the surface is severely incomplete: no splits, dividends, options, exchanges list, or other standard EODHD endpoints — just prices and fundamentals. As a general research/data platform it is broad rather than deep, mixing a decent question-answering core with unrelated one-off utilities, so no single coherent lifecycle is fully covered.

Resources