Skip to main content
Glama
oscardvs

Zoteus

by oscardvs
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Hybrid

Get attachment full text / passages / outline (read-only)

zotero_get_fulltext
Read-only

Get full text from Zotero PDFs/EPUBs to verify claims with page numbers. Use queries to find relevant passages, extract page ranges, or retrieve the outline.

Instructions

Retrieve an item's PDF or EPUB text for grounding. Pass a parent item_key (its best PDF/EPUB attachment is resolved automatically) or an attachment key. With query, returns the top relevant passages with locators (char offsets, nearest section, and a page); with page_range (e.g. "3-7"), returns just those pages, re-extracted from the PDF so the span is exact; with outline:true, returns the PDF's table of contents with page numbers (the cheapest way to decide which pages to read next); with none of them, returns a truncated head. Text comes from Zotero's full-text index when available; when the attachment is NOT indexed yet, the file itself is read and parsed on the fly (fallback, on by default; set fallback:false to disable), so a PDF added minutes ago still returns text (marked fulltextSource:"pdf" or "epub", with fileSource saying where the bytes came from). The file is read from the running Zotero desktop app, else straight out of the local Zotero storage folder, else downloaded from Zotero cloud storage. Page numbers are exact whenever the PDF was parsed, and otherwise an estimate (pageApprox) unless precise_pages:true. Read-only; the indexed text is served by the running Zotero desktop app when there is one, otherwise by the cloud Web API. Use this to cite a claim with a page after finding an item via zotero_search_items / zotero_semantic_search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoReturn top passages relevant to this query.
outlineNoReturn the PDF's table of contents (heading, page, nesting level) instead of text.
fallbackNoWhen Zotero has no indexed full text for the attachment, read the file itself and extract it directly (default true).
item_keyYesParent item key or attachment key.
max_charsNoBest-effort cap on total returned text (default 12000); a single passage is never split, so one passage may slightly exceed it.
library_idNo
page_rangeNoPage span like "3-7" (1-based, inclusive). PDFs only.
library_typeNo
max_passagesNoMax passages (default 5).
precise_pagesNoRe-extract the PDF for exact page numbers (already the default with `page_range`).

Schema Changelog

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

  1. Changed4 schema fields changedv1.13.0
    • changedInput schema / properties / fallback / description
      Previous value: -"When Zotero has no indexed full text for the attachment, download the PDF and extract it directly (default true)."New value: +"When Zotero has no indexed full text for the attachment, read the file itself and extract it directly (default true)."
    • addedInput schema / properties / outline
      Added value: +{
+  "description": "Return the PDF's table of contents (heading, page, nesting level) instead of text.",
+  "type": "boolean"
+}
    • changedInput schema / properties / page_range / description
      Previous value: -"Page span like \"3-7\" (1-based, inclusive)."New value: +"Page span like \"3-7\" (1-based, inclusive). PDFs only."
    • changedInput schema / properties / precise_pages / description
      Previous value: -"Re-extract the PDF for exact page numbers."New value: +"Re-extract the PDF for exact page numbers (already the default with `page_range`)."
  2. Changed1 schema field changedv1.3.1
    • addedInput schema / properties / fallback
      Added value: +{
+  "description": "When Zotero has no indexed full text for the attachment, download the PDF and extract it directly (default true).",
+  "type": "boolean"
+}
  3. First observedv1.0.4

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses fallback behavior (indexed vs on-the-fly parsing), source resolution order (desktop app, local storage folder, cloud storage), page-number exactness (exact vs pageApprox), and return markers (fulltextSource/fileSource). This is rich behavioral context.

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?

The description is long, but each clause earns its place given the tool's 10 parameters and multiple modes. It is front-loaded with the core action and then organized by behavior, fallback, sources, and precision; it could trim a little redundancy around read-only serving, but it remains efficient.

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 10-parameter tool with no output schema, the description covers all modes, defaults, source fallbacks, precision behavior, and return metadata. The only structured coverage missing (no output schema) is compensated by naming returned fields like fulltextSource, fileSource, and pageApprox.

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 coverage is 80%, and the description still adds substantial semantics: item_key accepts parent attachments resolved automatically, page_range is exact and PDF-only, outline is a cheap TOC view, precise_pages is already defaulted with page_range, and fallback materializes text from an unindexed file. It explains how the parameters interact, not just what they are.

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 opens with a specific verb and resource: 'Retrieve an item's PDF or EPUB text for grounding.' It then enumerates the four retrieval modes (query, page_range, outline, head), which makes the tool's scope unmistakable and distinguishes it from the sibling search tools by tying it to citing a claim after item discovery.

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?

It gives clear usage context: use it after zotero_search_items / zotero_semantic_search to ground citations with page numbers, and advises outline as the cheapest way to decide which pages to read next. It does not explicitly state when-not-to-use or name alternative full-text tools like zotero_fulltext, so it stops short of full five-level routing guidance.

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