Skip to main content
Glama
Sign In
zotero-rag

zotero-rag

by jolapodolszanska
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

update_index

Indexes new or modified Zotero PDFs since the last run so local semantic and BM25 search can query current full-text content.

Instructions

Index PDFs added or changed in Zotero since the last run (can take a few minutes for many new files).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose a meaningful trait: the operation can take several minutes for many new files, which signals latency/blocking risk. It does not say whether the call is idempotent, what happens to already-indexed items, whether it errors on locked libraries, or whether it runs asynchronously.

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?

A single sentence with the action front-loaded and the performance caveat in a parenthetical at the end. Every clause earns its place; nothing is padded or repeated from the title.

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?

Return values are covered by the output schema and there are no parameters to explain, so the description only needs to convey behavior and cost, which it does via the incremental scope and the multi-minute warning. It falls short of complete only in not clarifying blocking/asynchronous behavior or the relationship to index_status.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. No parameter-level meaning is missing because no parameters exist.

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 (index) and resource (PDFs added or changed in Zotero) with an explicit incremental scope ('since the last run'). It is clearly distinguishable from sibling index_status, though it does not name that sibling or any alternative explicitly.

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 phrase 'added or changed ... since the last run' implies the trigger condition (new/modified files) and the incremental nature of the call. However, it never states when not to use it, whether it must be re-run after each import, or that index_status is the way to check progress instead.

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