Skip to main content
Glama
dhamma-seeker

tripitaka-mcp

by dhamma-seeker
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

Keyword Search

search_by_keyword
Read-onlyIdempotent

Search the Pāli Tipiṭaka for exact words or phrases using trigram word-similarity. Filter by pitaka, language, and translation edition.

Instructions

Keyword search across the Pāli Tipiṭaka (trigram word-similarity).

Searches the configured enabled language(s) on the server. Filterable by pitaka and translation edition.

💡 Hints for the AI client: The system's canonical reference is Romanised Pāli (from SuttaCentral). If the user asks in a disabled or unsupported language, translate the keyword to Romanised Pāli (preferred) or English before calling this tool — e.g. "suffering" → "dukkha", "mindfulness of breathing" → "ānāpānassati". See the server instructions for the enabled language set.

🔍 Pick the right search tool for the question shape:

  • Term lookup (exact word appearances) — e.g. "occurrences of ānāpānassati": this tool is best (trigram nails the exact word).

  • Concept search ("discourses about X") — e.g. "discourses about mindfulness of breathing": use search_hybrid instead. Canonical Pāli has two quirks that hurt keyword search for concepts: • Section headings (Ānāpānapabba) often use a different word than the teaching body, which uses verb forms (assasati, passasati, dīghaṁ, rassaṁ). E.g. DN22's Ānāpānapabba has 16 segments but the word ānāpāna appears in only 2 (header + footer) — the actual teaching segments won't match. • Stock phrases (e.g. So satova assasati, satova passasati) recur in 10+ suttas, so a keyword query ranks broadly and won't pinpoint the canonical reference.

  • General keyword survey — set limit≥30 and filter client-side, or call multiple related forms (root verb + noun + compound).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordYesThe word/phrase to search for.
languageNoSearch language — must be in the server's ENABLED_LANGUAGES (default: "pali"). Disabled languages return an error.pali
editionNoThai translation edition — "dhiranandi", "jayasaro", "mbu", "royal" or None. Only used when language="thai" and Thai is enabled on the server.
pitakaNoFilter by pitaka — "vinaya", "sutta", "abhidhamma" or None (all). ✅ v1.1+: all three pitakas at parity with SuttaCentral bilara — see list_structure for live counts.
limitNoMaximum results (default: 10, max: 50).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

Beyond readOnlyHint, describes trigram matching, enabled language constraints, error behavior for disabled languages, and limitations for concept searches due to Pāli linguistic quirks.

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?

Well-structured with headings and emojis, but slightly verbose; the hints section could be more succinct while retaining value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Fully covers when and how to use, parameter details, sibling comparisons, and behavioral nuances, leaving no gaps for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All 5 parameters have schema descriptions (100% coverage), but the description adds practical context like translation hints, edition usage rules, and limit recommendations.

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?

Clearly states it performs keyword search across the Pāli Tipiṭaka using trigram word-similarity, and distinguishes itself from sibling tools like search_hybrid by specifying exact word matching.

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

Usage Guidelines5/5

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

Provides explicit guidance on when to use this tool (term lookup, keyword survey) versus alternatives (concept search → search_hybrid), including translation hints and filtering options.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dhamma-seeker/tripitaka-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server