Skip to main content
Glama
oscardvs

Zoteus

by oscardvs
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Hybrid

Zotero attachments (files)

zotero_attachment
Destructive

Upload, download, or inspect attachment files in Zotero: fetch from URL or local disk, save to a chosen path, or return item metadata.

Instructions

Upload, download, or inspect attachment files. action: "upload" stores a file as a Zotero attachment using the full File Storage protocol (provide url to have Zoteus fetch it, or file_path for a file on the machine running Zoteus; optional parent_item to attach it under an item, title, content_type) and returns the new attachment key; "download" fetches an attachment's file to a local path (provide item_key; optional save_path, default under the Zoteus data dir) and returns the path and byte count; "info" returns an attachment item's metadata. File bytes are written to / read from disk, never streamed through the conversation. Upload/download use the cloud Web API and your file-storage quota. When Zoteus runs on a different machine than Zotero, file_path refers to the server's disk, so use url instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoURL to download and upload instead of `file_path`; works on remote/hosted servers.
titleNo
actionYes
item_keyNoAttachment item key (download/info).
file_pathNoFile to upload, on the machine running Zoteus.
overwriteNoAllow `save_path` to replace a file that already exists (default false).
save_pathNoWhere to write the downloaded file.
library_idNo
parent_itemNoParent item key to attach under (upload).
content_typeNo
library_typeNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv1.14.0
    • addedInput schema / properties / overwrite
      Added value: +{
+  "description": "Allow `save_path` to replace a file that already exists (default false).",
+  "type": "boolean"
+}
  2. Changed2 schema fields changedv1.6.0
    • changedInput schema / properties / file_path / description
      Previous value: -"Local file to upload."New value: +"File to upload, on the machine running Zoteus."
    • addedInput schema / properties / url
      Added value: +{
+  "description": "URL to download and upload instead of `file_path`; works on remote/hosted servers.",
+  "format": "uri",
+  "type": "string"
+}
  3. First observedv1.0.4

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already mark the tool as non-read-only and destructive, and the description adds substantial context: file bytes are read/written to disk and never streamed through the conversation, upload/download consume cloud Web API and file-storage quota, and file_path refers to the server's disk. No contradiction with annotations exists.

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 definition opens with a concise one-line summary and then uses a structured, dense second sentence to cover all three actions, parameters, defaults, and caveats. Every clause adds either behavioral or parameter knowledge without padding.

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?

For a three-mode tool with no output schema, the description covers return values, disk behavior, quota usage, and the remote-host caveat well. It leaves minor gaps around library_id/library_type defaults and explicit overwrite behavior, but those are partially covered by the schema and annotations.

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 description adds real meaning beyond the schema for most action-relevant parameters: url vs file_path, parent_item, title, content_type, item_key, save_path default, and return forms. It does not clarify library_id/library_type selection, and schema coverage is only 55%, so it earns a 4 rather than a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence names the resource (attachment files) and three concrete verbs: upload, download, inspect. This makes the tool's purpose immediately clear, but it does not contrast it with the similarly named sibling zotero_attach_file, so it stops short of full sibling differentiation.

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?

The description gives per-action guidance: upload with url/file_path, download with item_key and save_path, info for metadata. It also provides a clear conditional rule to use url instead of file_path on remote hosts. However, it does not explicitly state when to prefer alternatives among sibling tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/oscardvs/zoteus'

If you have feedback or need assistance with the MCP directory API, please join our Discord server