Skip to main content
Glama
Sign In
zotero-brain-slim

zotero-brain-slim

by Feplus2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search_zotero_library

Search your Zotero library by keyword, title, or DOI to retrieve metadata for matching entries. Optionally limit results to a specific collection.

Instructions

检索 Zotero 文献库：按关键词/标题/DOI 搜索已有条目，返回元数据列表。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_zotero_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo最多返回条数，默认 20
queryYes关键词、标题片段或 DOI（10.xxx/yyy）
collection_keyNo限定 Collection key（可选）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It states the core action (search) and the return type (metadata list), which gives basic behavioral transparency. However, it does not mention read-only guarantees, error handling, or any other side effects, leaving room for more disclosure.

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 a single, complete sentence that front-loads the verb and resource. It contains no redundancy or filler, making it highly concise and well-structured.

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?

For a simple search tool with a comprehensive input schema, the description covers the essential aspects: what the tool does, what it searches for, and what it returns. It does not explain pagination or edge cases, but the limit parameter description already addresses result count. Overall, it is sufficiently complete for the tool's complexity.

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

Parameters3/5

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

The input schema provides 100% description coverage for all parameters, so the baseline is 3. The description adds no additional parameter semantics beyond what is already in the schema—'keywords/title/DOI' is exactly the same as the schema's '关键词、标题片段或 DOI'. Therefore, it does not compensate for any gaps.

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 uses a specific verb '检索' (search) and clearly identifies the resource as 'Zotero 文献库' (Zotero library). It mentions search by keyword/title/DOI and returning a metadata list, which distinguishes it from siblings like discover_papers by limiting scope to '已有条目' (existing items).

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

Usage Guidelines4/5

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

The phrase '检索已有条目' (search existing items) clearly implies this tool should be used for finding already-stored items in the Zotero library. However, it does not explicitly name alternatives or state when not to use it, but the context is clear enough for an AI agent.

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