Skip to main content
Glama

Eu Cellar

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Every document the Publications Office of the European Union publishes — legislation, treaties…

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.3% over 22 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-eu-cellar
GitHub Stars
0
Server Listing
eu-cellar

TDQS

A3.8/5.0

Scored across 39 tools

Disambiguation2/5

Several tools have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded share identical routing but differ only in minor behavior, and deep_research / bet_research / validate_claim all perform multi-source grounded lookups that agents will struggle to choose between. The prediction-market tools (polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, release_calendar_markets) also overlap in opportunity finding and risk checking, and the descriptions themselves rely on 'PREFER OVER' instructions rather than clean separation.

Naming Consistency3/5

Most names are snake_case, but the convention is not a consistent verb_noun pattern: some are noun_noun (cellar_work, company_facts, ai_visibility_check), some use prefixes (cellar_, pipeworx_), and the ask_pipeworx family uses suffix variations (beta, grounded). The mix is readable but not predictable, and the odd 'cellar_search_works' breaks the pattern.

Tool Count2/5

39 tools is far above the 15-tool sweet spot and even above the 25-tool heavy threshold, and the set is a sprawling mashup of EU Cellar document access, Pipeworx meta-routing, prediction-market analytics, memory, subscriptions, AI visibility, and dependency scanning. Many tools could be collapsed (e.g. the three ask_pipeworx variants) or are so niche they bloat the surface for a server named 'Eu Cellar'.

Completeness3/5

For the EU Cellar subdomain, the three tools (search, SPARQL, metadata lookup) provide reasonable coverage of search, structured query, and record retrieval, though full-text download or update/delete operations are absent. Across the whole server the domain is unclear, so assessing completeness is difficult; the Pipeworx meta-tools are comprehensive but compete with each other rather than forming a tight lifecycle.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedrelease_calendar_markets2 fields changed
      • addedOutput schema / properties / empty_reason
        Added value: +{
+  "description": "Present ONLY on a zero-release window: \"no_releases_in_window\". The window was queried and nothing is scheduled — this is an answer, not a failure.",
+  "type": "string"
+}
      • addedOutput schema / properties / hint
        Added value: +{
+  "description": "Present ONLY on a zero-release window: what to change (usually a wider `hours`).",
+  "type": "string"
+}
  2. 39 tool updates
    • First observedai_visibility_check
    • First observedask_pipeworx
    • First observedask_pipeworx_beta
    • First observedask_pipeworx_grounded
    • First observedbet_research
    • First observedcellar_search_works
    • First observedcellar_sparql
    • First observedcellar_work
    • First observedcompany_facts
    • First observedcompare_entities
    • First observeddeep_research
    • First observeddiscover_tools
    • First observedentity_profile
    • First observedforget
    • First observedgenerate_llms_txt
    • First observedkalshi_weather_edge
    • First observedlist_subscriptions
    • First observedpipeworx_feedback
    • First observedpipeworx_trending
    • First observedpolymarket_arbitrage
    • First observedpolymarket_edge_tracker
    • First observedpolymarket_edges
    • First observedpolymarket_fill_risk
    • First observedpolymarket_kalshi_spread
    • First observedrecall
    • First observedrecent_alerts
    • First observedrecent_changes
    • First observedrelease_calendar_markets
    • First observedremember
    • First observedresolution_audit
    • First observedresolution_diff
    • First observedresolve_entity
    • First observedscan_competitor_ai_presence
    • First observedscan_dependency
    • First observedsearch_within
    • First observedsubscribe
    • First observedsuggest_questions
    • First observedunsubscribe
    • First observedvalidate_claim

Related MCP Connectors

Related MCP Servers

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