Skip to main content
Glama

Zotero Get Page Layout

zotero_get_page_layout

Detects figures, tables, and display equations on a PDF page, returning normalized coordinates with captions and a ready-made annotation call. Use it to locate annotation areas instead of guessing.

Instructions

Detect figure, table and display-equation regions on one PDF page and return their boxes (x, y, width, height, normalized 0-1), each with its caption or equation number, a confidence and a ready-made zotero_create_annotation call. Use it before an area annotation instead of guessing coordinates. Boxes cover the graphic itself: labels inside a figure or unruled table headers can fall outside, and confidence reflects caption matching, not box completeness. attachment_key: the PDF attachment, NOT the parent item (zotero_get_item_children lists it). page: 1-indexed. PDFs only.

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": {
      "attachment_key": "<attachment_key>",
      "page": "<page>"
    },
    "name": "zotero_get_page_layout"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYes
attachment_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does well: it discloses that boxes cover only the graphic (labels inside figures or unruled table headers can fall outside) and that confidence reflects caption matching rather than box completeness. Those are non-obvious caveats an agent could not infer. It does not mention whether the call is purely read-only or what happens on a page with no detected regions, leaving a small gap.

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?

Purpose and return values are front-loaded, then usage, then caveats, then parameter notes — a sensible order with no filler sentences. The parameter notes are packed into terse prose clauses rather than a clean list, which makes the final third slightly denser than ideal, but nothing is wasted.

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, no-output-schema, no-annotation tool, the description covers purpose, invocation preconditions, return contents, and accuracy limitations. An agent has everything needed to call it correctly and interpret the result without opening the schema.

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 must compensate, and it does for both parameters: attachment_key is explicitly the PDF attachment rather than the parent item, with a pointer to the sibling that lists it, and page is stated as 1-indexed. These are exactly the semantics the bare integer/string 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 description opens with a specific verb and resource: 'Detect figure, table and display-equation regions on one PDF page and return their boxes.' It also enumerates the returned fields (x, y, width, height, caption/equation number, confidence, ready-made annotation call), which no sibling tool offers, so an agent can separate it from zotero_read_pdf_pages or zotero_get_annotations immediately.

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 states a clear when-to-use rule ('Use it before an area annotation instead of guessing coordinates') and a hard scope limit ('PDFs only'), and it routes the agent to zotero_get_item_children for obtaining the attachment key. It stops short of saying what to do when no regions are detected or when another tool would be preferable, so it is strong but not exhaustive.

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