Skip to main content
Glama

Zotero Write Capabilities

zotero_write_capabilities

Checks whether Zotero writes are supported and what credentials or setup are missing, so you can choose the right authorization step before asking users.

Instructions

Report whether this server can write to Zotero (local API, web API, hybrid, or not at all) and what is missing. Instant; opens no dialog. Call it when a write tool reports no writable backend, before asking the user: if local writes are supported but no key is held, call zotero_authorize_local_writes; otherwise web API credentials are needed.

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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden; it usefully discloses that the call is instant and opens no dialog, and explains what the report contains. It could more explicitly state that the tool never mutates Zotero state, but the diagnostic framing and 'opens no dialog' note make the safe, read-only nature clear enough.

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?

Three sentences, front-loaded with the core purpose and immediately followed by behavioral and routing details. Every sentence earns its place: what it reports, that it is instant/no-dialog, and when to call it with alternatives.

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-parameter diagnostic with no output schema or annotations, the description states the possible capability outcomes and says it reports what is missing. It also tells the agent exactly what to do next depending on the result, making the definition complete for its complexity.

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 are no parameter meanings to document beyond the baseline. The description correctly adds no unnecessary parameter discussion for a no-argument capability check.

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 ('Report') and resource ('whether this server can write to Zotero') and enumerates the possible capability states (local API, web API, hybrid, not at all). It clearly distinguishes this diagnostic tool from sibling write tools such as zotero_add_item and zotero_batch_update.

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?

It gives an explicit trigger ('when a write tool reports no writable backend'), a timing instruction ('before asking the user'), and routes the agent to zotero_authorize_local_writes when local writes are supported but no key is held, or to web API credentials otherwise. This is precise when-to-use and alternative-routing guidance.

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