Skip to main content
Glama
Sign In
matricula-mcp

matricula-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

matricula_register

Read-only

Read one register to get its description, citation, and page labels with viewer links, so you can cite genealogical sources accurately.

Instructions

Read one register: its description, citation, and every page's label and viewer link.

A page's url opens it in Matricula's own viewer for a person to read; page is the image's position, the number to cite with the label. A label (e.g. '02-Taufe_0001', '001-03_0004-r') is a finding aid naming the section or folio; it is not a date. A register with no pages shows no images, often because the law closes it.

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": {
      "register": "<register>"
    },
    "name": "matricula_register"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoPages to list (1-1000).
firstNoFirst page to list, 1-based.
refreshNoTrue asks Matricula again instead of using the cache, and replaces the cached copy. Lists are kept 28 days, parish and register pages 7, searches 1.
registerYesA register key from matricula_registers, e.g. 'oesterreich/salzburg/krimml/TFBI', or its Matricula address.
label_containsNoKeep pages whose label contains this, e.g. 'Index' or '0041'.

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 already cover the read-only and open-world profile, and the description adds substantive behavior: it warns that a label is a finding aid rather than a date, and explains that a register with no pages usually reflects legal closure of the material. It does not mention auth, rate limits, or truncation when count is smaller than the page set.

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?

It is front-loaded with the action and result, and the following sentences each carry interpretive value about url, page, and label. It is dense but every sentence earns its place; only the label examples are slightly over-elaborated.

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?

With no output schema, the description correctly shoulders the job of explaining the return shape and the meaning of the empty case. It leaves minor gaps around pagination totals and whether the response indicates more pages remain.

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 every parameter (count, first, refresh, register, label_contains) is already documented, including the cache lifetimes. The description adds no new parameter-level meaning; its explanatory text describes returned fields rather than inputs, so the baseline 3 applies.

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?

The first sentence gives a specific verb and resource ('Read one register') and enumerates the returned content (description, citation, page labels and viewer links). It implicitly contrasts with matricula_registers by operating on a single register key, but never names a sibling 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 implied rather than stated: the register parameter description points to matricula_registers as the source of the key, which signals the prerequisite call. There is no explicit when-to-use, when-not-to-use, or redirection to matricula_page_image for per-image work.

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

Deploy Server

Other Tools