Skip to main content
Glama
Sign In
taaghche-mcp

taaghche-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Book details

tg_book
Read-onlyIdempotent

Fetch a single Taaghche book's details by ID: price in Toman, format, pages or duration, people, rating breakdown, categories, ISBN, and author/publisher slugs.

Instructions

One book: price, format, pages or duration, people, rating breakdown, categories, ISBN.

Gives author_slugs and publisher_slug for tg_author / tg_publisher.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "book_id": "<book_id>"
    },
    "name": "tg_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
book_idYesBook id, e.g. 6426.
description_charsNoDescription length cap.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds value by previewing returned fields and the cross-tool slug linkage, but says nothing about failure behavior for an invalid book_id, whether records can be missing, or how 'people' and 'rating breakdown' are shaped.

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 with the payload summary front-loaded and the linkage note second; nothing is padding. The terseness costs a little clarity where bare nouns like 'people' are left unexplained, but the structure is efficient.

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?

With no output schema, the description carries the burden of describing returns and does so as a partial field list, which is helpful. It leaves gaps on the ambiguous fields ('people', 'rating breakdown'), record-not-found behavior, and the effect of description_chars truncation, so a caller must still infer some behavior.

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 description coverage is 100%, so book_id and description_chars are already fully documented with bounds, defaults, and an example. The description adds no further meaning about either parameter, which is the baseline 3 case when the schema does the heavy lifting.

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 single resource ('One book') and enumerates exactly what comes back (price, format, pages/duration, people, rating breakdown, categories, ISBN), which separates it from list-oriented siblings like tg_browse and tg_search. It stops short of an explicit verb, but the intent is unambiguous.

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

Usage Guidelines3/5

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

Usage is only implied: fetch by id for a single book, then feed the returned author_slugs/publisher_slug into tg_author or tg_publisher. That chaining hint is genuinely useful, but there is no stated when-to-use versus tg_search, tg_browse, or tg_similar, and no exclusion of cases where a lookup will fail.

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