Skip to main content
Glama
lazyants

transkribus-mcp-server

by lazyants
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create Document from METS

transkribus_coll_create_doc_from_mets

Create a collection document from METS XML by providing inline XML or a local file path, uploaded as multipart form data.

Instructions

Create a document in a collection from a METS XML document, uploaded as multipart form data. Provide exactly one of metsXml or metsFilePath.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collIdYesCollection ID
metsXmlNoInline METS XML content
metsFilePathNoLocal file path to a METS XML file

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv4.0.0
    • removedInput schema / properties / fileName
      Removed value: -{
-  "description": "METS file name",
-  "type": "string"
-}
    • addedInput schema / properties / metsFilePath
      Added value: +{
+  "description": "Local file path to a METS XML file",
+  "type": "string"
+}
    • addedInput schema / properties / metsXml
      Added value: +{
+  "description": "Inline METS XML content",
+  "type": "string"
+}
    • removedInput schema / properties / title
      Removed value: -{
-  "description": "Document title",
-  "type": "string"
-}
  2. Addedv3.1.0
  3. Removedv3.0.0
  4. First observedv2.1.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this is a non-readonly, open-world, non-idempotent, non-destructive write. The description adds useful context (multipart upload, exactly-one-source constraint) but says nothing about permissions required, cost implications, or side effects of repeated calls.

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

Conciseness5/5

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

Two sentences, no waste, with the core action front-loaded and the input constraint immediately following. Every clause earns its place.

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

Completeness3/5

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

The absence of an output schema means the description could usefully say what a successful call returns (e.g., document ID), and it omits prerequisites like collection permission. Adequate for invoking the tool but not fully complete for a creation operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so field meanings are covered, but the description adds the mutual-exclusivity rule ('exactly one of metsXml or metsFilePath') that the schema does not encode via anyOf/oneOf. That is genuine semantic value beyond the structured fields.

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 (create) and resource (document in a collection) with the source format (METS XML) and transport (multipart form data). The multipart phrasing implicitly distinguishes it from the sibling transkribus_coll_create_doc_from_mets_url, though siblings iiif/ftp are not named.

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?

Implies usage through source format and the upload mechanism, but never states when to prefer this tool over the sibling create_doc_from_mets_url, iiif, or ftp variants. No exclusions or prerequisites are given, leaving the selection decision 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