Skip to main content
Glama
Sign In
matricula-mcp

matricula-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

matricula_search

Read-only

Locate the parish a village belonged to by searching Matricula's place index against parish descriptions and archive village lists; register entries are excluded.

Instructions

Search Matricula's place index: which parishes name this place.

It matches parish names and the village lists and histories archives wrote into parish descriptions (snippet shows where), so it finds the parish a village belonged to. It never searches the registers' entries: no name of a person is found this way. Searches are slow by design, at least ten seconds apart.

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": {
      "place": "<place>"
    },
    "name": "matricula_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoMost parishes to return (1-100).
placeYesA place name, e.g. 'Altenmarkt'. Matricula matches whole words.
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.
sectionNoKeep only parishes in this section, e.g. 'oesterreich/gurk'.
to_yearNoWith from_year: the last year.
from_yearNoWith to_year: only parishes with registers in these years.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Beyond readOnlyHint/openWorldHint, it discloses a real operational constraint — searches are 'slow by design, at least ten seconds apart' — which materially shapes how an agent should call it. It also explains the matching semantics (whole-word matches on parish names plus village lists/history prose) and that `snippet` shows where the match came from. Cache behavior is left to the schema's `refresh` description.

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?

Front-loaded with the one-line purpose, then progressively adds matching semantics, the exclusion, and the rate limit. Every sentence carries information; the line breaks into a short paragraph keep it readable without padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description names `snippet` and explains what it indicates, covers the matching model, the hard exclusion, and the rate limit, while annotations cover the safety profile and the schema covers all six parameters. Nothing essential for a correct call appears to be missing.

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 schema already carries full parameter meaning (count range, section format, year pairing, cache semantics). The description adds nothing about individual parameters, but it does surface `snippet`, an output field not in any schema. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Search Matricula's place index') and immediately scopes it ('which parishes name this place'). It also explicitly distinguishes itself from register searching: 'It never searches the registers' entries', so an agent can tell it apart from matricula_register/matricula_registers without opening a schema.

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?

Gives a clear when-not: it finds the parish a village belonged to, and does not find person names. That exclusion is the key usage discriminator here. It stops short of naming the sibling tool to use instead for person/register lookups, leaving that routing to inference.

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