Skip to main content
Glama

Free books

tg_free_books
Read-onlyIdempotent

Browse and retrieve free Persian ebooks and audiobooks priced at zero, sorted by popularity by default, with filters for format, category, and pagination.

Instructions

Free books and audiobooks (price 0), most downloaded first by default.

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

Input Schema

NameRequiredDescriptionDefault
sortNohot = trending; cheapest = ascending price.most_downloaded
cursorNoPrevious next_cursor.
formatNoany
categoryNoCategory id (e.g. 68) or slug from tg_categories; empty = all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the meaningful behavioral fact that results are restricted to price 0 and default to most-downloaded order, but says nothing about pagination behavior, result volume, or currency assumptions behind 'price 0'.

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?

A single front-loaded sentence with no filler — the defining constraint (price 0) and the default ordering are both stated immediately. Nothing is redundant or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter listing tool with annotations and no output schema, the essentials are present, but the description is thin relative to four filter parameters — it never clarifies how category interacts with 'free', or that cursor drives pagination. An agent can call it, but must read the schema to understand the full filtering surface.

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 75%, with the sort enum and cursor already well documented in the schema itself. The description only reinforces the default sort value and the price-0 filter; it adds no meaning to format, category, or cursor beyond what the schema states. Baseline 3 is appropriate given the schema does most of the work.

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 names a specific resource and scope: free books and audiobooks at price 0, with the default ordering stated. That distinguishes it reasonably from tg_bestsellers and tg_new_releases, though it never explicitly contrasts itself with those siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to choose this tool over tg_browse, tg_search, or tg_bestsellers — the free/price-0 constraint is implied by the title rather than framed as a selection condition. No exclusions or prerequisites are given, so the agent must infer that this is the 'browse free catalog' entry point.

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