Skip to main content
Glama

Książki cytowane przez autora

list_books
Read-only

List books and ancient sources cited in archive articles, showing where each can be read free and legally or noting copyright. Filter by author, title, or article ID.

Instructions

Lists books and ancient sources cited in the archive's articles, with information where they can be read for free and legally (or that they are copyrighted). Filter by a search phrase (author/title) or by article id. Books available in full in the built-in library can be read with read_book.

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": "list_books"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoFragment autora lub tytułu, np. „Platon”, „Däniken”
article_idNoPokaż książki cytowane w tym artykule

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.9/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read. The description adds genuinely useful disclosure beyond that — that results include where each book can be read for free and legally, or a copyright flag — which matters since there is no output schema. It still says nothing about result volume, ordering, or whether the two filters combine.

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?

Two sentences, front-loaded with what the tool returns, then the filters, then the sibling pointer. The parenthetical '(or that they are copyrighted)' is slightly clunky but carries real meaning about the availability field.

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 list tool with no output schema, the description conveys the result entity and the key availability payload. The remaining gap — pagination or result size — is minor given the low complexity and the read-only annotation.

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 coverage is 100% and both parameters already carry descriptions with examples, so the schema does the heavy lifting. The description restates the two filter modes (author/title phrase, article id) without adding format, matching behavior, or combinability details, which is the baseline for high coverage.

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 — 'Lists books and ancient sources cited in the archive's articles' — plus a distinctive detail about free/legal versus copyrighted availability. This is clearly distinguishable from read_book, which is explicitly named as the way to read full texts.

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 the two filtering modes (by author/title search phrase, or by article id) and routes the agent to read_book for full texts in the built-in library. It does not say when to prefer this over list_library or search, so a sibling exclusion is missing, but the context provided is clear.

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