Skip to main content
Glama
Sign In
zotero-rag

zotero-rag

by jolapodolszanska
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_items

List indexed Zotero works with optional tag, author, collection, and year-range filters, returning each item's key, citation, and title one per line.

Instructions

List indexed works (optionally filtered), one per line: item_key, citation, title.

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

Input Schema

NameRequiredDescriptionDefault
tagNo
authorNo
year_toNo
year_fromNo
collectionNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; 'List' implies a read operation and it discloses the per-line output format. However, it says nothing about result limits, ordering, pagination, or whether the full index is returned.

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 front-loaded sentence with zero waste; the core action and output shape come first and nothing is padded.

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

Completeness2/5

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

For a tool with five undocumented filter params and no annotations, the description is too thin; filter semantics (exact match vs substring, year range inclusivity, combining filters) are unaddressed. The existing output schema does relieve it of explaining return values.

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

Parameters2/5

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

Five filter parameters (tag, author, year_from, year_to, collection) have 0% schema description coverage, and the description only says 'optionally filtered' without naming a single field or its combination semantics. The agent must infer meaning entirely from parameter names.

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 and resource ('List indexed works') and describes the output shape ('one per line: item_key, citation, title'). It is distinguishable from siblings like search_library and get_item by being a bulk listing, though it never names those alternatives explicitly.

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

Usage Guidelines2/5

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

'Optionally filtered' implies the filters exist but gives no guidance on when to use this versus search_library or search_within_item. No prerequisites, exclusions, or selection criteria are stated.

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