Skip to main content
Glama

Read one record, routed by the archive its identifier names

get_item
Read-onlyIdempotent

Retrieve a complete archive record using its identifier, including what it is, who made it, and what you can read. Returns reuse terms and supports paginated text and optional sections.

Instructions

Read one record in full from the archive its identifier names: what it is, who made it, when, what the archive says about it, and what a reader can open. 'identifier' must come from search_inside or search_items. It names the archive, so this reads the right one without guessing; a string no archive would have minted is refused, and a shape more than one archive mints is refused rather than sent to a guess, because sending it anywhere answers about the wrong thing. Terms of reuse come back on every read and belong to that record alone. A record stating none has granted nothing, and silence is never read as permission. 'sections' decides what else comes back, and the answer names what was left out and what this archive files nothing under: a field empty because nobody asked for it is a different thing from a field the archive never fills. Long prose is returned one window at a time: 'text_offset' says where to resume, and a window ends at a line boundary. An offset past the end says so rather than answering with an empty description. An answer can take several seconds, because one of the archives publishes a request ceiling this server keeps to.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionsNoWhich parts to return besides the record's identity and its terms of reuse.
identifierYesFrom a search, such as 'archive:mobydickorwhale01melv' or 'loc:sn83030214/1900-01-01/ed-1/seq-1'.
max_copiesNoCopies to list. The answer says how many more the record holds.
text_offsetNoWhere to resume in the record's prose, in characters from its start.
max_text_charsNoCharacters of prose to return. The text block shows roughly the first 1400 of them and the whole window is in the structured output. The answer says where to resume.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemYes
notesYes
id_read_asYesHow a raw identifier was routed, when it was not spelled with its archive.
text_windowYesWhich part of the record's prose this answer carries.
sections_omittedYesSections this call did not ask for. A field belonging to one of these is empty for that reason alone.
sections_returnedYes
fields_not_read_from_this_archiveYesFields this server reads nothing into from this archive. A field named here is empty for every record it returns, which is a different thing from a record that left it blank.
Behavior5/5

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

Beyond the readOnlyHint and idempotentHint annotations, the description reveals important behaviors: how identifiers route to archives, refusal logic for malformed identifiers, terms-of-reuse semantics (silence not being permission), pagination via text_offset with line-boundary windows, and a notable latency warning. This adds significant context that annotations alone don't cover.

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 lengthy but well-structured, front-loading the core purpose and then layering usage constraints, edge cases, and performance notes. Each sentence contributes substantively, though some legal/rights caveats could be considered slightly peripheral. It's efficient for the tool's complexity.

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?

Given the complex routing logic and multiple parameters, the description covers all usage aspects: source of identifier, refusal behavior, rights handling, field absence vs. emptiness, prose windowing, and latency. The output schema handles return values, so the description needn't repeat them, making it complete.

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?

With 100% schema coverage, the schema already describes each parameter, but the description adds meaning: sections controls optional parts and reports which fields are absent vs. empty, text_offset behavior is clarified with line boundaries and out-of-range handling, and max_copies/max_text_chars implications are tied to the windowing. This elevates understanding beyond the schema.

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 opening sentence 'Read one record in full from the archive its identifier names' clearly identifies the operation and resource. It also lists the record fields ('what it is, who made it, when...') and contrasts with sibling search tools, making the tool's specific role unambiguous.

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 explicitly states the identifier must come from search_inside or search_items, establishing a prerequisite and an implicit alternative workflow. It also explains routing refusal for invalid/ambiguous identifiers, which helps the agent know when the tool will fail. It doesn't explicitly name alternatives but clearly implies searching before reading.

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/smeet666/mcp-books'

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