Skip to main content
Glama

Search

search
Read-onlyIdempotent

Search the Europeana collection by keyword. Returns matching items with ids (pass an id to record), titles, creators, dates and image links.

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": {
      "query": "rembrandt"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-based, default 1).
limitNoMax results (1-100, default 20).
queryYesKeyword(s), e.g. "rembrandt", "ceramics", "moon landing".
_apiKeyNoEuropeana API key (auto-injected by the platform; or pass your own).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
      -  {
      -    "_apiKey": "your-europeana-api-key",
      -    "query": "rembrandt"
      -  },
      -  {
      -    "_apiKey": "your-europeana-api-key",
      -    "limit": 50,
      -    "page": 1,
      -    "query": "ceramics"
      -  }
      -]New value: +[
      +  {
      +    "query": "rembrandt"
      +  },
      +  {
      +    "limit": 50,
      +    "page": 1,
      +    "query": "ceramics"
      +  }
      +]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "_apiKey": "your-europeana-api-key",
      +    "query": "rembrandt"
      +  },
      +  {
      +    "_apiKey": "your-europeana-api-key",
      +    "limit": 50,
      +    "page": 1,
      +    "query": "ceramics"
      +  }
      +]
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds value beyond that by disclosing the shape of returned items (ids, titles, creators, dates, image links), which matters because there is no output schema. It omits result-count/pagination behavior and any API-key or rate-limit caveats.

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, zero waste, with the resource scope front-loaded and the return-value detail following it. Nothing is repeated from the schema.

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 simple read-only search tool with no output schema, the description covers scope, inputs (via schema) and return fields, which is most of what an agent needs. It could still say whether results are paginated and what an empty result looks like.

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 description coverage is 100%, including page (1-based, default 1), limit (1-100, default 20) and query examples, so the baseline is 3. The description adds no syntax or meaning beyond the schema; 'pass an id to record' refers to result ids, not to an input parameter.

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?

States a specific verb and resource: keyword search over the Europeana collection, plus what a result item contains. It does not distinguish itself from the similarly named sibling search_within or from other search-style siblings like company_register_search, so the agent must infer which index this covers.

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?

Usage is only implied by the resource name ('Europeana collection by keyword'). There is a helpful workflow pointer ('pass an id to record'), which is a next-step hint rather than an alternative-selection rule. No when-not-to-use case or explicit naming of a competing tool such as search_within.

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.