Skip to main content
Glama
Sign In
taaghche-mcp

taaghche-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Browse a category

tg_browse
Read-onlyIdempotent

Browse and list Taaghche books by category, sort, format, price ceiling, or free/discounted status, with paginated catalog results for filtering and discovery.

Instructions

List books of a category (or the whole catalog), 16 per page, by sort, format and price ceiling.

max_price scans up to 5 pages (scanned); exact with sort='cheapest'. For words use tg_search.

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

Input Schema

NameRequiredDescriptionDefault
sortNohot = trending; cheapest = ascending price.hot
cursorNoPrevious next_cursor.
formatNoany
categoryNoCategory id (e.g. 68) or slug from tg_categories; empty = all.
free_onlyNo
max_priceNoMax price, Toman.
discounted_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive browsing, so the safety profile is covered. The description adds genuinely non-obvious behavior: a fixed 16-item page and, critically, that max_price filtering is approximate, scanning up to 5 pages with a `scanned` signal unless sort='cheapest'. That approximation caveat is the kind of trait an agent cannot get from structured fields.

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 short sentences, front-loaded with the primary action and ending on the sibling hand-off. The max_price sentence is compressed to near-cryptic ("scans up to 5 pages (`scanned`)"), trading a little clarity for density, but nothing is filler.

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 7-parameter browse tool with no output schema, the definition covers the query side well but leaves the result side thin: pagination is described only via the 16-per-page figure, and it never states that approximately-filtered results may omit matching books. Adequate to call correctly, not fully complete.

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?

At 57% schema coverage the description must carry some weight, and it does explain that category may be empty (whole catalog) and that max_price is in Toman with scan-based semantics. However, free_only, discounted_only and format get no meaning beyond their names, and cursor behavior (next_cursor round-trip) is only implied by the schema text.

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 ("List books of a category"), names the scope expansion ("or the whole catalog"), and pins down page size and the faceting dimensions. The closing clause "For words use tg_search" makes the boundary against the most confusable sibling explicit.

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?

Gives a clear when-to-use rule (browse by category/sort/filter) and one explicit exclusion routing keyword lookups to tg_search, plus the conditional that sort='cheapest' makes max_price exact. It does not mention when to prefer tg_bestsellers, tg_new_releases or tg_free_books, which overlap with sort/filter combinations.

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