Skip to main content
Glama
polish-archives-mcp

polish-archives-mcp

by ianderso

poznan_search

Read-only

Search Poznań Project marriage records from 1800–1899 in Wielkopolska and Kujawy by surnames, given names, years, and confession to locate spouses, parents, and original register holders.

Instructions

Search the Poznań Project's marriages, 1800-1899, Wielkopolska and Kujawy.

Each row has the parish, entry and year, groom and bride with ages and parents, how closely each surname matched, and who holds the original register. Given names are matched to the project's name groups (Joannes / Jan / Johann); a name in no group returns the groups. Too many matches come back as too_many_results, never as a zero.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "poznan_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage of 50 rows, from 1.
refreshNoTrue asks the site again instead of using the cached answer (kept a day).
year_toNoLast year, 1800-1899.
thresholdNoLeast similarity, 50-100; 70 catches more spellings.
year_fromNoFirst year, 1800-1899.
confessionNoKind of register; civil is the Standesamt (USC).any
any_surnameNoInstead of the two surnames: a surname of either spouse.
bride_givenNoBride's given name, any language.
groom_givenNoGroom's given name, any language.
bride_surnameNoBride's surname (maiden or widow's).
groom_surnameNoGroom's surname.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnly and openWorld, so the description must carry the rest — and it does usefully: it describes what each row contains (parish, entry, year, names, ages, parents, match tightness, holding archive), explains the given-name grouping behavior (Joannes/Jan/Johann, unmatched names return the groups), and discloses the too_many_results path rather than an empty result. It omits caching and pagination behavior, which live only in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, scope first, then result shape, then matching/edge-case behavior — well front-loaded with no filler. Slightly dense phrasing ('never as a zero', 'a name in no group returns the groups') costs a little clarity.

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 an 11-parameter, no-output-schema search tool, the description covers the essential unknowns: what comes back, how names are matched, and what happens on overflow. Pagination and cache controls are covered by the schema, so the remaining gap is guidance on sibling selection rather than missing call-critical detail.

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%, so the baseline is 3. The description adds modest meaning on given-name matching semantics and surname match scoring, but says nothing about threshold, any_surname vs paired surnames, confession, or refresh behavior that isn't already in the schema.

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 — searching the Poznań Project's marriage registers — and bounds it by date range and region (Wielkopolska and Kujawy). That regional/dataset framing implicitly separates it from other genealogy search siblings, but it never names or contrasts with them explicitly.

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 scope statement: an agent can infer this is for Polish marriage records in 1800-1899 in that region. There is no statement of when to prefer this over geneteka_search or basia_search, nor any coverage limits that would tell an agent when to look elsewhere.

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