Skip to main content
Glama
Sign In
uleszka

uleszka

by jokerwader
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Biblioteka dawnych źródeł

list_library
Read-only

Lists public-domain ancient and historical works cited in the archive so you can identify texts available for reading, passage lookup, or library search.

Instructions

Lists the built-in library: full texts of ancient and historical works cited by the author that are in the public domain (Plato's Timaeus and Critias, Herodotus, Genesis, Ovid, the Book of Enoch, Popol Vuh, Gilgamesh, Hammurabi, Book of the Dead, Strabo, Pliny, Mahabharata, Ramayana, Nostradamus, Charles Fort and more). Use read_book / find_in_article / search(scope='biblioteka') on them.

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_library"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.2/5.0
Behavior4/5

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

readOnlyHint=true already establishes safety, and the description adds what the annotation cannot: the collection is public-domain full texts cited by the author, with a partial inventory of titles. It does not state the response shape or ordering, but for a zero-parameter static listing that gap is minor.

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 purpose is front-loaded in the first clause, which is good, but the long parenthetical of ~15 titles inflates the sentence well past what an agent needs to decide whether to call it. The trailing 'and more' signals the enumeration is non-exhaustive, further reducing the value of naming every work.

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 read-only, parameterless listing with no output schema, the description supplies enough: what the library is, roughly what it holds, and which tools to use on the results. Only the return format/ordering and whether the corpus is fixed are left unstated, which are marginal for this complexity.

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?

The tool takes zero parameters, so there is no argument semantics to explain; baseline 4 applies. The description correctly does not waste words on inputs and instead spends them on what the list contains.

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?

States a specific verb and resource ('Lists the built-in library') and immediately scopes it: full texts of ancient/historical works cited by the author, in the public domain. The enumerated examples (Plato, Herodotus, Gilgamesh, etc.) make the boundary of the collection concrete, distinguishing it from a general catalog.

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 names the follow-up tools explicitly — 'Use read_book / find_in_article / search(scope=\'biblioteka\') on them' — which tells the agent this is a discovery/index step feeding the readers. It does not explicitly contrast with sibling list_books or list_articles, so the agent must infer that this is the built-in corpus rather than the author's own books.

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