Skip to main content
Glama
alejooroncoy

Campus

by alejooroncoy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

campus_research_read_document

Read-onlyIdempotent

Read public academic documents from HTTPS URLs into bounded, section-based evidence for research tasks, preserving CSV/XLSX coordinates and routing PDFs to a page reader.

Instructions

Read a public HTTPS academic document in PDF, HTML, plain text, Markdown, XML/JATS, DOCX, EPUB, CSV or XLSX into bounded section-based evidence. CSV rows and XLSX sheet, row and cell coordinates are preserved; formulas are not recalculated. PDF is routed to the specialised page reader. ZIP files require format=docx, epub or xlsx. Maximum 20 MB; does not bypass paywalls, logins or DRM.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
formatNoUse auto for HTML, text, XML, CSV and PDF. For a ZIP file, specify docx, epub or xlsx explicitly.auto
sectionCountNo
startSectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.2
    • changedInput schema / properties / format / description
      Previous value: -"Use auto for HTML, text, XML and PDF. For a ZIP file, specify docx or epub explicitly."New value: +"Use auto for HTML, text, XML, CSV and PDF. For a ZIP file, specify docx, epub or xlsx explicitly."
    • changedInput schema / properties / format / enum
      Previous value: -[
-  "auto",
-  "html",
-  "text",
-  "markdown",
-  "xml",
-  "jats",
-  "docx",
-  "epub"
-]New value: +[
+  "auto",
+  "html",
+  "text",
+  "markdown",
+  "xml",
+  "jats",
+  "docx",
+  "epub",
+  "csv",
+  "xlsx"
+]
  2. Addedv2.0.1

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/destructive, so the bar is lower, yet the description adds real operational context: the 20 MB ceiling, that it does not bypass paywalls, logins or DRM, that formulas are not recalculated, and that CSV/XLSX coordinates are preserved. These are exactly the behavioral traits an agent needs and cannot infer from annotations.

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?

Front-loaded with the core action and format list, then layered with constraints (ZIP, size, legal limits). Dense but every sentence carries distinct information; slight overrun in enumerating formats twice (once in the opening list, once for routing rules).

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?

With no output schema and a complex multi-format tool, the description covers formats, routing, bounds and legal constraints well, but the section-based chunking parameters (sectionCount/startSection) are only obliquely referenced, so an agent lacks full guidance on how to page through a large document.

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?

Schema coverage is only 25%, so the description must compensate, and it does for format: it explains that auto covers HTML/text/XML/CSV/PDF and that ZIP requires an explicit docx/epub/xlsx. It implies sectionCount/startSection through 'bounded section-based evidence' but never explains pagination or the sectionCount/startSection relationship, leaving a partial gap.

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?

Names a specific verb (Read) and resource (a public HTTPS academic document) plus the format set, and explicitly distinguishes itself from the sibling campus_research_read_pdf by stating 'PDF is routed to the specialised page reader.' An agent can route between read_document, read_pdf and read_indexed_pdf without opening a 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?

Gives concrete conditions: ZIP files require format=docx/epub/xlsx, and PDF goes to the specialised reader. It does not explicitly name when NOT to use this tool (e.g. vs read_source_file) or state prerequisites beyond the paywall/login exclusion, so it falls short of full when/when-not guidance.

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

Deploy Server

Other Tools