Skip to main content
Glama
Sign In
matricula-mcp

matricula-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

matricula_sections

Read-only

Lists Matricula Online countries and their sections—dioceses and archives—so you can choose the correct section key for parish searches.

Instructions

List Matricula's countries and, in each, its sections: the dioceses and archives.

A section's key is what matricula_parishes takes. parishes is Matricula's own count. The first call for every country reads about a dozen pages, two seconds apart; after that the list is cached for four weeks.

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": "matricula_sections"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoOne country: its key ('oesterreich', 'LU'), German name or English name. Empty lists every country.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, the description discloses the real cost profile: the first call per country fetches roughly a dozen pages with two seconds between requests, and the result is cached for four weeks with refresh replacing the cache. That latency and caching context is exactly what an agent needs to decide when to call and whether to set refresh.

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?

Purpose is front-loaded in the first sentence, followed by the key chaining fact and then the caching cost. The only blemish is an awkward paragraph break mid-sentence after 'archives', but there is no filler wording.

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 does the necessary work of naming the returned shape: countries, sections as dioceses and archives, the section key, and the `parishes` field as Matricula's own count. A few more returned fields would make it airtight, but an agent has enough to call and interpret it.

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 coverage is 100%, so the country and refresh parameters are already fully documented in the schema, including accepted key/name formats and cache lifetimes. The description adds only the section-key linkage to matricula_parishes, which is closer to output semantics than parameter meaning, so baseline 3 applies.

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 ('List Matricula's countries and, in each, its sections: the dioceses and archives') and explicitly differentiates the result from the sibling by noting a section's key is what matricula_parishes takes. An agent can tell this apart from matricula_parishes without inspecting either 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?

Implies a clear workflow: call this to obtain a section key, then pass it to matricula_parishes, and use refresh when a fresh pull is wanted rather than the cached list. It stops short of an explicit 'do not use this if...' exclusion, so it lands just under the top mark.

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