Skip to main content
Glama

Similar books

tg_similar
Read-onlyIdempotent

Find related books by similar works, author, or publisher using a book ID, and compare their price, format, and rating.

Instructions

Related books in lists (similar works, same author, same publisher): price, format, rating.

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

Input Schema

NameRequiredDescriptionDefault
book_idYesBook id, e.g. 6426.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds that results are grouped into lists by relation type with price, format and rating attached, which is useful behavioral context. It still says nothing about result limits, ordering, or what happens when a book has no relations.

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?

One short sentence, front-loaded with the primary noun and followed by the qualifying relation types and output fields. It is efficient, though the colon-separated field list reads as a fragment rather than complete prose.

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?

This is a simple read-only lookup with one fully documented parameter and no output schema, and the description conveys both the relation categories and the per-item fields. For this level of complexity that is close to sufficient; only result-count and pagination expectations are unstated.

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?

There is only one parameter, book_id, and the schema fully documents it at 100% coverage including an example value. The description adds no constraint or format detail beyond the schema, so the baseline of 3 applies.

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 states a specific resource ('related books') and enumerates the relation types (similar works, same author, same publisher) plus the fields returned. That distinguishes it from a plain book lookup like tg_book, though the telegraphic phrasing leaves the exact retrieval semantics somewhat implicit.

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 explicit when-to-use guidance, no statement of prerequisites beyond the required book_id, and no routing to alternatives such as tg_author or tg_book. The agent must infer from the name and the parenthetical relation list that this is the tool for discovering related titles.

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