Zotero-MCP

by RogerAylagas

Overview Schema Source Related Servers Discussions Admin

Python

Local

zotero_list_styles

List available CSL citation styles, with an optional query to filter by name or keyword for quick lookup.

Instructions

List available CSL citation styles.

Args: query: Filter by substring, e.g. "chicago", "medical", "nature".

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

Input Schema

Name	Required	Description	Default
`query`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the burden of disclosing behavior. It explicitly says 'List', indicating a read-only operation, and describes the query as a substring filter. This is sufficient for a simple listing tool; no side effects or prerequisites are stated, but none are expected.

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 focused sentence plus a brief parameter explanation, with no wasted words. The purpose is front-loaded, and the parameter example adds value without redundancy.

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?

This is a simple 1-parameter tool with an output schema, so the description does not need to detail return values. The description covers the core behavior (listing styles) and the filtering semantics, which is complete enough for an agent to invoke it correctly. Sibling tools provide context but do not require explicit differentiation.

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 input schema only provides the type and default for 'query' with no description. The tool description compensates fully by explaining that the parameter filters by substring and providing concrete examples ('chicago', 'medical', 'nature'), giving the agent a clear understanding of how to use it.

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 action ('List') and the specific resource ('available CSL citation styles'), distinguishing it from sibling list tools like zotero_list_collections or zotero_list_tags by the unique resource type. The purpose is immediately understandable.

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 when to use the tool (when needing a list of citation styles) but does not explicitly mention alternatives or exclusion cases. There is no guidance on when not to use it or why it might be preferred over other list tools, though the resource-specific nature makes the usage fairly obvious.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.