Skip to main content
Glama
SVerITG

Metis

by SVerITG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Metis · Librarian — Index Pdf Library

index_pdf_library

Extracts and indexes full text from PDFs in literature and Zotero storage, processing only unindexed files so research content becomes searchable.

Instructions

Extract and index full text from all PDFs in the Metis library.

Reads PDFs from inputs/literature/ and Zotero storage.
Stores first 4000 characters per paper in library_fulltext table.
Also updates literature_metadata.abstract for any matched papers.
Incremental — only processes files not yet indexed.

Args:
    scope: "literature" = inputs/literature/ only | "zotero" = Zotero storage only | "all" = both

Input Schema

NameRequiredDescriptionDefault
scopeNoall

Output Schema

NameRequiredDescriptionDefault
resultYes

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?

With no annotations provided, the description carries full burden and discloses key behaviors: reads PDFs, stores first 4000 characters, updates abstracts, and is incremental. It does not mention destructive actions, but the mutation of metadata is transparently described.

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?

The description is well-structured with clear bullet points and an Args section. It is front-loaded with the main purpose. Could be slightly more concise, but overall effective.

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?

Given the presence of an output schema (not shown but indicated), the description does not need to explain return values. It sufficiently covers inputs, behavior, and incremental nature. No gaps identified.

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?

The description includes an 'Args' section that explains the possible values for the single parameter 'scope' (literature, zotero, all), which the schema only defines as a string with no enums or description. This adds significant meaning beyond the schema.

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 clearly states the tool extracts and indexes full text from PDFs in the Metis library, specifying sources (inputs/literature/, Zotero storage) and storage destinations. It differentiates itself by mentioning incremental processing and scope parameter.

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?

The description implies usage for indexing PDFs but does not provide explicit guidance on when to use this tool versus alternatives like 'index_library_pdfs' or 'scan_literature'. No when-not-to-use or prerequisites are mentioned.

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