Skip to main content
Glama

Europeana

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.3/5.0
Behavior4/5

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

Annotations declare readOnly=true, idempotent=true, destructive=false. Description adds value by stating scoping to identifier (IP, key hash, account ID) and pairing with remember/forget. No contradictions.

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 concise sentences. First sentence states core action, second provides usage context and examples. No wasted words.

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?

Given one optional parameter, annotations covering all relevant hints, and no output schema, the description is complete. It explains purpose, usage, scoping, and relationships to sibling tools.

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 already has 100% coverage with description for 'key'. Description reinforces the 'omit to list all keys' behavior, but adds little beyond schema. Baseline 3 is appropriate.

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?

Description clearly states verb+resource: 'Retrieve a value... or list all saved keys'. Distinguishes from siblings (remember, forget) by explicitly mentioning them. Examples illustrate real use cases.

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?

Describes when to use: to look up context stored earlier. Provides examples (ticker, address, notes) and mentions scoping. Doesn't explicitly say when not to use, but sibling tools cover alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Europeana 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

Many tools have overlapping purposes, e.g., three versions of ask_pipeworx for similar tasks, and several research/analysis tools (bet_research, deep_research, entity_profile) with unclear boundaries. The mix of Europeana-specific tools with a broad research toolkit creates confusion.

Naming Consistency2/5

Tool names are inconsistent, mixing snake_case (ai_visibility_check, ask_pipeworx), verb_noun patterns (compare_entities, resolve_entity), and short names (search, record, forget). No clear naming convention is followed throughout the set.

Tool Count2/5

33 tools is excessive for a Europeana-focused server, as only 3 tools (search, record, search_within) are directly related to Europeana. The rest are a broad, unrelated toolkit, making the server feel like a kitchen sink rather than a cohesive collection.

Completeness2/5

The Europeana-specific tool surface is severely incomplete, lacking browse collections, advanced filters, or entity linking. The inclusion of many unrelated tools does not compensate for the gaps in the core domain, resulting in a poorly scoped offering.

Resources