zotero-mcp-local-write

zotero_item_fulltext

Get the full text content of any Zotero item by providing its item key, allowing direct access to the complete text of papers or attachments for reading and analysis.

Instructions

Get the full text content of a Zotero item, given the item key of a parent item or specific attachment.

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": {
      "item_key": "<item_key>"
    },
    "name": "zotero_item_fulltext"
  }
}

Input Schema

Name	Required	Description	Default
`item_key`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Sep 2, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. 'Get' clearly signals a read-only retrieval operation and states what is returned, but it does not disclose behavior when fulltext is unavailable, whether authentication is needed, or any additional response context. This is adequate for a simple getter but not rich.

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, well-structured sentence with no filler. It front-loads the action and resource, then clarifies the required input in a natural and compact way.

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?

Given the tool's simplicity—one required parameter, a clear read-only purpose, and an existing output schema—the description is nearly complete. The main gap is the lack of usage exclusions or alternative-routing guidance, but this is minor for a straightforward fulltext retrieval tool.

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 only names the parameter 'item_key' with no description, so the description compensates by explaining that the key can refer to either a parent item or a specific attachment. This adds meaningful semantic guidance. It still does not specify the key format, but the extra context is valuable.

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 identifies the action ('Get'), the resource ('full text content of a Zotero item'), and the key input ('given the item key of a parent item or specific attachment'). This distinguishes it from sibling tools like zotero_item_metadata, which retrieves metadata, and zotero_download_file, which downloads files.

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 the tool should be used when an agent has a known Zotero item key and needs the full text content. However, it does not explicitly state when not to use it or mention alternatives such as zotero_item_metadata for metadata or zotero_download_file for binary attachments.

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