Skip to main content
Glama

Browse a book

gj_book
Read-onlyIdempotent

Browse a book or section by listing its sub-books and poems with first couplets, 30 per page, so you can pick a poem to open.

Instructions

Sub-books and the poems of one book or section, each with its first couplet, paged by 30.

Open a poem with gj_poem.

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": {
      "cat_id": "<cat_id>"
    },
    "name": "gj_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage of poems, 30 per page.
cat_idYesBook or section id (cat_id from gj_poet or a poem's book).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered elsewhere. The description adds genuinely new behavioral detail: results are paged at 30 per page and each entry is truncated to its first couplet, which warns the agent that full poem text requires a follow-up call. What it omits is anything about page-bound behavior at the 1000-page ceiling or ordering of sub-books versus poems.

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

Conciseness5/5

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

Two sentences, roughly twenty words, with the returned content and page size front-loaded and the follow-up tool named last. Nothing is redundant, and the navigation hint is short enough not to crowd out the core purpose.

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?

There is no output schema, so the description has to convey the return shape, and it does: sub-books plus poems with first couplets, paginated. Combined with fully documented parameters and rich annotations, an agent has what it needs to call this correctly. The only gap is how sub-books and poems are ordered or interleaved within a page.

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 (cat_id and page) are already documented, including the 30-per-page meaning of page and where cat_id comes from. The description's 'paged by 30' merely restates the schema, and it adds no meaning about cat_id provenance beyond what the schema says. 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 the exact resource returned: the sub-books and the poems of a single book or section, each accompanied by its first couplet, delivered in pages of 30. That is specific enough to distinguish it from gj_poem, which the description also names as the drill-down tool. It stops short of an explicit verb ('browse' appears only in the title), so it is clear but not maximally sharp.

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 an explicit routing instruction for the next step: 'Open a poem with gj_poem,' which tells the agent this tool returns listings, not poem bodies. It does not state when to prefer this over search-oriented siblings such as gj_search or gj_find_verse, so the guidance covers the drill-down path but not the discovery-vs-navigation choice.

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