Skip to main content
Glama

Zotero Authorize Local Writes

zotero_authorize_local_writes

Requests permission to write to the local Zotero library when a write fails without a key, then waits for the user's Zotero dialog choice before continuing.

Instructions

Ask the user to allow writes to the local Zotero library (Zotero 10+). BLOCKS until they answer a dialog in the Zotero app, so tell them to switch to Zotero first. 'Always Allow' saves a reusable key; 'Allow' covers one write. Call it when a write fails and zotero_write_capabilities says local writes are supported but no key is held. app_name: shown in the dialog. timeout: seconds to wait (5-55, default 45). Zotero allows about 5 prompts a minute: do not retry in a loop.

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

Input Schema

NameRequiredDescriptionDefault
timeoutNo
app_nameNoZotero MCP

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

No annotations are supplied, but the description takes on the full behavioral burden. It discloses that the call BLOCKS until the user answers a dialog, that the user must switch to Zotero first, the difference between 'Always Allow' (reusable key) and 'Allow' (one write), and a rate limit of about 5 prompts a minute with an explicit warning not to retry in a loop.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Every sentence adds useful information, and the text leads with purpose, then the blocking warning, then the trigger condition. It is still a dense single paragraph with no line breaks, so an agent scanning for the blocking warning has to parse the entire block.

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 two-parameter authorization tool with no output schema, the description covers everything an agent needs: when to call, that the call blocks, what user action is required, what each choice grants, and how to avoid hitting the prompt rate limit.

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?

Schema description coverage is 0%, so the description has to explain both parameters, and it does. It says app_name is 'shown in the dialog', and timeout is in seconds with the valid range 5-55 and a default of 45, which adds the range constraint the schema omits.

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 definition opens with a concrete verb and resource: "Ask the user to allow writes to the local Zotero library (Zotero 10+)." It also scopes the tool to local library writes and a specific Zotero version, so an agent will not confuse it with zotero_write_capabilities or with remote/library write tools.

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 a precise trigger: call it when a write fails and zotero_write_capabilities says local writes are supported but no key is held. This not only names the sibling but also states the condition that selects it, so the agent does not need to guess when to use this tool.

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