Skip to main content
Glama

New releases

tg_new_releases
Read-onlyIdempotent

Browse new book releases, filtered by category or format, with cursor-based pagination to continue through results.

Instructions

Newest books first, overall or per category.

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

Input Schema

NameRequiredDescriptionDefault
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

C2.7/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 one genuine behavioral fact beyond that — results are ordered newest-first — but says nothing about pagination limits, result size, or what happens when the category matches nothing.

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?

It is a single short sentence fragment with no wasted words, but the brevity is under-specification rather than disciplined concision — front-loading the newest-first ordering while dropping the verb and the return semantics.

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 simple 3-parameter read-only listing tool with full annotation coverage, the description is only just adequate: it explains sort order and category scope but leaves the format filter undocumented in both schema and description, and gives no sense of the paginated response.

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

Parameters2/5

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

Schema coverage is 67%, and the one sentence present essentially restates the category parameter's own schema description ("empty = all"). The format parameter (any/ebook/audiobook) has no description in the schema and is never mentioned, so the description fails to close the 33% gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Newest books first, overall or per category" communicates the ordering guarantee and the scope, which goes beyond the bare title "New releases," but it never states a verb or what the tool actually returns (a paginated list of book records). An agent can guess it is a sorted listing of new titles, but the resource shape has to be inferred.

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?

The phrase "overall or per category" hints that a category filter is optional, but there is no guidance on when to prefer this over tg_bestsellers, tg_search, or tg_browse, and no exclusions. Given the large sibling set, routing between them is left entirely to inference.

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