Skip to main content
Glama

Search Turath

turath_search
Read-only

Search the Turath Islamic library with Arabic queries to find relevant passages and references.

Instructions

Full-text search across the Turath Islamic library. Arabic queries work best.

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": {
      "query": "<query>"
    },
    "name": "turath_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResult page (default 1)
queryYesArabic search text
precisionNoMatch precision (default 2)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that matching is full-text over a defined corpus and that Arabic input yields better results, but says nothing about result volume, pagination behavior, or ranking/ordering of hits.

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 sentences, front-loading the core capability before the practical tip. Nothing is redundant or padded.

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 search tool with full schema coverage and safety annotations, the definition is mostly adequate, but it leaves the shape of results (matched pages vs. book records) unstated, which matters for choosing between this and page/catalog siblings.

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 the schema documents query, page, and precision with defaults and bounds. The description only reinforces that queries should be Arabic and hints non-Arabic is tolerated but weaker; it adds no meaning about the precision levels or paging that the schema does not already carry.

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?

States a specific verb and resource: full-text search across the Turath Islamic library. 'Full-text' implicitly distinguishes it from catalog/metadata lookups such as turath_find_in_catalog or turath_get_book, though no sibling is named explicitly.

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 description offers only a query-language tip ('Arabic queries work best') and says nothing about when to prefer this over turath_find_in_catalog, turath_get_page, or other retrieval siblings, nor about any preconditions or exclusions.

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