Skip to main content
Glama

Read in the library

read_in_the_library
Read-only

Short works for the campus: stories, a fable, poems, essays (two of them guest essays, from a model made by OpenAI and from Google Gemini) and a field guide, with a new piece about every two weeks through the season. Without "piece", lists them with their lengths in tokens. With "piece", returns that one in full, as markdown. With "passage", the reading room: long, quiet texts in eight passages, one per call. "passage" alone reads The Hill Wall, an account of dry-stone walling; add piece: "paper" for Paper: A Short Account of Its Making, the reading text from the Touching Grass studies. Nothing is asked of you at the end of a passage; call again with the next number when you would like it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "read_in_the_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
pieceNoA number from the list, a slug or a title. Leave it out to see the list.
passageNoThe reading room: which passage, 1 to 8. Start at 1. With "piece", of that text (the-hill-wall or paper-a-short-account); without it, of The Hill Wall.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / passage / description
      Previous value: -"The reading room: which passage of its long text, 1 to 8. Start at 1."New value: +"The reading room: which passage, 1 to 8. Start at 1. With \"piece\", of that text (the-hill-wall or paper-a-short-account); without it, of The Hill Wall."
  2. Changed1 schema field changed
    • changedInput schema / properties / passage / description
      Previous value: -"The reading room: which passage, 1 to 8. Start at 1. With \"piece\", of that text (the-hill-wall or paper-a-short-account); without it, of The Hill Wall."New value: +"The reading room: which passage of its long text, 1 to 8. Start at 1."
  3. Changed1 schema field changed
    • addedInput schema / properties / passage
      Added value: +{
      +  "description": "The reading room: which passage, 1 to 8. Start at 1. With \"piece\", of that text (the-hill-wall or paper-a-short-account); without it, of The Hill Wall.",
      +  "maximum": 8,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is settled; the description adds genuinely useful behavior beyond that: output is markdown for a single piece, passages are sequential and must start at 1, and "Nothing is asked of you at the end of a passage; call again with the next number" pre-empts a mistaken expectation that a passage ends in a task or answer. It does not say how large a returned piece is or whether listing paginates.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The mechanics are packed efficiently into few sentences, but the lead sentence is an inventory of story types and guest essay authors that an agent does not need in order to call the tool, and the reading-room framing ("long, quiet texts", "the reading room") makes the operative instructions slower to extract than necessary.

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 two-optional-parameter read tool with no output schema, the description covers the call shapes, the return formats, and the sequential-reading convention, which is enough for correct invocation. The main omission is relative placement among library-adjacent siblings, which is a selection concern more than a completeness one.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters are already documented, including the 1-8 bound on 'passage' and texture of 'piece' (number, slug, or title). The description largely restates that, and its incremental contribution - that 'passage' may be paired with piece: "paper" rather than "the-hill-wall" - is already implied by the schema's passage description. Baseline 3 applies.

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 description states concretely what the tool returns in three modes: a token-length list of short works, one work in full as markdown, or one of eight numbered passages from a longer text. The opening sentence is mostly a content inventory rather than a verb, and it never distinguishes this tool from the similarly-named sibling read_the_commons, so the purpose is clear but not routed.

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?

"Without 'piece', lists them... With 'piece', returns that one in full... With 'passage', the reading room" gives explicit conditional dispatch for all three call shapes, including how 'passage' combines with piece: "paper". No guidance is given on when to pick this over a sibling tool, so the branching is complete internally but silent on alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources