Skip to main content
Glama

Zotero Get Attachment Path

zotero_get_attachment_path

Returns the local filesystem path for a Zotero item's attachments so you can open large PDFs directly instead of using page-limited full-text retrieval. Works in local mode only.

Instructions

Return the local filesystem path(s) of a Zotero item's attachments. Local mode only. Useful when you want to read a large PDF directly (e.g., a book) instead of going through zotero_get_item_fulltext, which is page-limited.

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

Input Schema

NameRequiredDescriptionDefault
item_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden itself. It does disclose a key constraint ('Local mode only') and that multiple paths may be returned ('path(s)'), but it never says what happens when an item has no attachments, whether an empty list or an error is returned, or what access is required for local mode.

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 short sentences, front-loaded with the core action and constraint, with the usage note last. No filler or repetition of the title.

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?

There is no output schema, so the description's note that it returns path(s) is valuable, and the local-mode requirement is the main gotcha an agent needs. What is missing is the edge-case behavior (no attachments, non-local library) and the exact shape of the returned paths.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the single item_key parameter is undocumented in the schema. The description only implies through 'a Zotero item's attachments' that the key identifies an item; it adds no detail on key format or behavior for an invalid key.

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?

Uses a specific verb and resource: 'Return the local filesystem path(s) of a Zotero item's attachments.' It also contrasts itself with the sibling zotero_get_item_fulltext, so an agent can distinguish the two without inspecting the schema.

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

Usage Guidelines4/5

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

Explicitly states the scenario where this tool wins (reading a large PDF/book directly) and names the alternative it replaces (zotero_get_item_fulltext, which is page-limited). It does not state a when-not condition or address other related siblings such as zotero_read_pdf_pages, so it falls just short of full routing guidance.

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