Skip to main content
Glama
Sign In
matricula-mcp

matricula-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

matricula_page_image

Idempotent

Saves a Matricula register page image with its citation when image access is enabled; if disabled, returns an images_not_enabled response with viewer link, label, and citation without writing a file.

Instructions

Save one page image with its citation, if the operator has turned image access on.

Image access is off unless ICARUS has granted it: Matricula's image host refuses scripted requests. While it is off, this answers images_not_enabled with the page's viewer link, label and citation, and writes nothing. When on, the file is a new .jpg, not hidden, not under ~/Library, and inside the operator's download folder when one is set.

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_page_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoThe page's position, 1-based, as matricula_register gives.
registerYesA register key, e.g. 'oesterreich/salzburg/krimml/TFBI', or a page's viewer address (?pg=N).
destinationNoAbsolute path of a new .jpg file, e.g. '/path/to/images/krimml-12.jpg'. Used only when image access is on.

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?

Goes well past the annotations: it discloses the upstream host refusing scripted requests, the gating grant, that nothing is written and an `images_not_enabled` payload is returned when off, and concrete properties of the written file (new .jpg, not hidden, not under ~/Library, inside the download folder when set). That is exactly the behavioral context annotations cannot express.

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 action and its gating condition, then the off-path, then the on-path file constraints. Sentences earn their place, though a couple of the file-property clauses are more detail than most agents need before calling.

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 carries the return burden and does describe the failure payload, but it never says what a successful save returns (path, citation format, existing-file behavior). For a write-side tool that gap is minor but real.

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 schema already documents page, register and destination, including that destination is used only when image access is on. The description adds no format, defaulting or validation meaning beyond that, so the 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?

Names a specific verb and resource ('Save one page image with its citation') and immediately scopes it with the enabling condition. The sibling tools are all listing/reading surfaces, so a page-image fetch/save is clearly distinguishable from them.

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?

Explains the exact condition that must hold before it does anything useful (ICARUS-granted image access) and what to expect when that condition fails. It does not name an alternative tool for the off case, but it makes clear the call still returns the viewer link, label and citation, so the agent is not left guessing.

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