Skip to main content
Glama
SVerITG

Metis

by SVerITG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Metis · Librarian — Import Zotero Pdfs

import_zotero_pdfs

Copies PDFs from a Zotero collection into a knowledge layer for indexing, covering texts behind publisher checks or institutional logins. Reads your local Zotero database without an API key.

Instructions

Copy the PDFs from a Zotero collection into a knowledge layer, so they get indexed.

For texts a background pack cannot download — anything behind a publisher's
browser check or your institution's subscription. Save them in Zotero with the
browser connector (logged in through your library), then point this at the
collection. No Zotero API key needed; it reads your local Zotero database.

The files are COPIED, so your Zotero library is left untouched. Indexing is not
run here — press Rebuild on the Library surface, or wait for the nightly index.

Args:
    collection: Zotero collection name, exactly as it appears in Zotero.
    database:   Slug of the knowledge layer to add them to (e.g. 'ph-foundations').
    confirm:    True to actually copy. Without it you get the list only.

Input Schema

NameRequiredDescriptionDefault
confirmNo
databaseYes
collectionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

A5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so well: files are copied, not moved; the Zotero library is untouched; no API key is needed; the local Zotero database is read; indexing must happen elsewhere; and confirm=False returns only a list.

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?

The description is front-loaded with the core purpose, then explains usage context, behavior, and parameters in that order. Every sentence adds useful information and the Args block is compact and easy to scan.

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?

For a three-parameter copy/import tool with no annotations and an output schema present, the description covers the essential context: when to use it, what it does and does not do, how the Zotero side is handled, and how confirm changes behavior.

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

Parameters5/5

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

Schema coverage is 0%, so the description must compensate, and it does: collection is the exact Zotero collection name, database is the knowledge-layer slug, and confirm=True is required to actually perform the copy while omitting it yields only a list.

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?

The description states a specific verb and resource: copying PDFs from a named Zotero collection into a knowledge layer so they can be indexed. This clearly distinguishes the tool from indexing siblings such as index_pdf_library or sync_zotero_local by clarifying that it copies local files and does not run indexing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says when to use it: for texts a background pack cannot download because of publisher browser checks or institutional subscriptions. It also gives the prerequisite workflow (save in Zotero via the browser connector), states that indexing is not run here, and explains the confirm=False preview behavior.

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