Zotero MCP

Zotero Write Capabilities

zotero_write_capabilities

Checks whether Zotero writes use local API, web API, hybrid, or no backend, so you can pick the right fix when a write tool reports no writable backend.

Instructions

Report whether and how this server can write to Zotero: local API, web API, hybrid (local reads + cloud writes), or nothing. Read-only and instant — it never opens a dialog. Call it when a write tool reports that no writable backend is configured, to find out which fix applies before asking the user for anything: if the local server supports writes but no key is held, call zotero_authorize_local_writes; otherwise web API credentials are needed. Takes no arguments. Example: zotero_write_capabilities().

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_write_capabilities"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

A4.9/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and delivers: it states the call is read-only, instant, and never opens a dialog. This is important behavioral context because the tool name could misleadingly suggest a write action, and it reassures the agent there are no interactive side effects.

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?

Every sentence earns its place: the capability scope, behavioral safety, trigger condition, follow-up routing, parameter note, and example. The most important information is front-loaded and the routing guidance is kept tight.

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?

For a zero-argument diagnostic whose output shape is already covered by an output schema, the description covers what the tool reports, when to call it, and what to do next. Nothing an agent needs to decide between this tool and its siblings is missing.

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 input schema is empty and the description confirms 'Takes no arguments' with an example call. There is nothing further to document, so this earns the zero-parameter baseline; the explicit no-arguments statement adds slight reassurance but not new semantic information.

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 opens with a specific verb and resource: 'Report whether and how this server can write to Zotero' and enumerates the exact possible outcomes (local API, web API, hybrid, nothing). It also distinguishes itself from the many write-oriented siblings by explicitly framing the call as a read-only diagnostic, so an agent will not mistake it for a write operation.

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

Usage Guidelines5/5

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

Usage is explicitly conditional: call it when a write tool reports no writable backend, before asking the user for anything. It even routes the follow-up action by naming zotero_authorize_local_writes for the local-no-key case and specifying web API credentials otherwise.

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

Deploy Server