Open Archives

Search Transcriptions

search_transcriptions

Read-only

Full-text search across page transcriptions

Performs a full-text search across the page transcriptions of historical documents indexed by Open Archives. Mirrors the search UI at /transcripties/zoek.php. Results are ordered by Elasticsearch relevance (the order is fixed and cannot be overridden) and are returned paginated. Each match includes a source citation, page identifier and up to five highlighted text fragments. The set of facets returned depends on the supplied filters.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "search_transcriptions"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes
`lang`	No
`start`	No
`year_end`	No
`year_start`	No
`number_show`	No
`archive_code`	No
`archive_number`	No
`inventory_number`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 31, 2026

TDQS

A4.3/5.0

Behavior5/5

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

The description adds substantial behavioral detail beyond the annotations: results are fixed-ordered by Elasticsearch relevance, paginated, and each match includes a source citation, page identifier, and up to five highlighted fragments. It also discloses that facets depend on supplied filters, providing valuable context that annotations alone do not convey.

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?

The description is three sentences long, front-loaded with the core purpose, and every sentence adds value: what it does, how it behaves, and what results look like. No redundant or fluff content.

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?

Given the tool has 9 parameters and no output schema, the description covers the essential behavior (search, ordering, pagination, match contents, facets) but does not elaborate on pagination parameters (start, number_show) or filter specifics. It is sufficient for a search tool but leaves some gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema coverage, the description must compensate by explaining parameter meanings, but it only vaguely refers to 'supplied filters' without detailing specific parameters like q, lang, start, number_show, year_start, or archive_code. The description does not add meaningful semantics beyond the parameter names themselves.

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 the tool performs a full-text search across page transcriptions, with a specific verb ('search') and resource ('page transcriptions'). It also distinguishes itself from siblings like search_records (which searches records) and show_transcription (which shows a single transcription), making its purpose unambiguous.

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?

The description provides clear context by noting it mirrors the search UI at /transcripties/zoek.php and explains the search behavior. However, it does not explicitly state when not to use this tool or name alternative tools, so it falls short of a 5.

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

All Open Archives tools Inspect

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.