Skip to main content
Glama
Sign In
taaghche-mcp

taaghche-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Search suggestions

tg_suggest
Read-onlyIdempotent

Suggests up to 10 matching book titles with IDs from a title or author prefix, helping you find books before checking prices with tg_search.

Instructions

Typeahead: up to 10 matching book titles with id. For prices use tg_search.

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": {
      "term": "<term>"
    },
    "name": "tg_suggest"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYesStart of a title or author.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds useful behavioral context beyond annotations: a maximum of 10 results and inclusion of book IDs in the response.

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?

Two short, front-loaded fragments convey the core behavior and the alternative with no unnecessary wording.

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?

For a simple one-parameter, read-only lookup with no output schema, the description supplies enough context: result cap, returned IDs, and an alternative for prices. Ordering or ranking of suggestions is not explained, but that is a minor gap.

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 100%, so the schema already explains that the term is the start of a title or author. The description adds no parameter-specific meaning and slightly narrows the result framing to book titles, while the schema allows author prefixes.

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?

The description states a specific behavior: a typeahead search returning up to 10 matching book titles with IDs. It distinguishes itself from tg_search for price lookups, so an agent can tell what this tool is for.

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?

It clearly positions the tool as a typeahead and explicitly redirects price-related queries to tg_search. It lacks broader guidance on when to prefer full search over typeahead, but the main alternative is named.

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