Skip to main content
Glama
Sign In

Open Archives

by io.github.coret
OverviewDiscussionsAdmin

Match Record

match_record
Read-only

Match a person to birth and death records

Searches the genealogical dataset by exact name and birth year and returns the Open Archives URIs of birth records, death records and registrations in which the person is mentioned.

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": {
      "name": "<name>",
      "birthyear": "<birthyear>"
    },
    "name": "match_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo
nameYes
birthyearYes

Schema Changelog

Changes observed during successful MCP inspections.

  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 readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description adds useful behavioral context: it searches by exact match criteria and returns specific URIs. No contradictions with annotations, and no mention of rate limits or auth, but the added detail about return content is valuable.

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 two sentences, with the first providing a succinct summary and the second adding detail. It is front-loaded and contains no filler or redundant information.

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 3-parameter tool with no output schema, the description adequately covers what the tool does and what it returns (Open Archives URIs). Gaps include handling multi-match cases and clarifying the 'lang' parameter, but overall the tool is sufficiently contextualized for an agent.

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 0%, so the description must compensate. It explains the 'name' and 'birthyear' parameters as search criteria, but does not explain the 'lang' parameter (enum nl/en). This partial explanation is helpful but leaves one parameter semantically undocumented, warranting a mid-range score.

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's purpose: matching a person to birth/death records by exact name and birth year, and returning Open Archives URIs. It specifies a precise verb ('match'/'searches') and resource ('genealogical dataset'), distinguishing it from sibling tools like generic search or record retrieval.

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 implies when to use the tool: when you have a person's exact name and birth year and want associated record URIs. However, it doesn't explicitly mention alternatives or exclusions, such as when to use search_records instead. The context is clear but lacks explicit 'when not to use' guidance.

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

All Open Archives toolsInspect
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