Skip to main content
Glama

Get Word Definition

get_word_definition
Read-onlyIdempotent

Look up the dictionary meaning of a Pāli word, with sutta context.

Serves as a Pāli Dictionary Bridge — pairs the "definition" with the "context where the Buddha actually used the word".

📖 About the dictionary sources: This tool draws from multiple primary dictionaries, including "พจนานุกรมพุทธศาสน์ ฉบับประมวลศัพท์" (Buddhist Dictionary — Concept-Glossary edition) by Somdet Phra Buddhaghosacariya (P. A. Payutto). The Thai-language entries are original scholarly works (not translations), so they are always available even when ENABLED_LANGUAGES has Thai disabled. The AI client should translate Thai entries into the user's language if needed.

🔀 Two kinds of thing in one payload. definitions[] come from the dictionaries, not the canon, so they carry no segment_id; appears_in_context[] is corpus text and does carry one. related_words[] are headwords holding your query as a substring, so opposites appear — dhamma returns adhamma. Context examples are drawn at random: two identical calls return different ones.

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": {
      "word": "<word>"
    },
    "name": "get_word_definition"
  }
}

Input Schema

NameRequiredDescriptionDefault
wordYesWord to look up (e.g. "dukkha", "กฐิน").
languageNoDictionary language (e.g. "en", "thai", or "all" as default).all
limit_contextNoNumber of sutta-context examples to include (1-5).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / language / enum
      Added value: +[
      +  "en",
      +  "thai",
      +  "th",
      +  "all"
      +]
  2. Changed3 schema fields changed
    • changedInput schema / properties / language / description
      Previous value: -"ภาษาของพจนานุกรม (เช่น \"en\", \"thai\", หรือ \"all\" เป็นค่าเริ่มต้น)"New value: +"Dictionary language (e.g. \"en\", \"thai\", or \"all\" as\n      default)."
    • changedInput schema / properties / limit_context / description
      Previous value: -"จำนวนตัวอย่างประโยคในพระสูตรที่จะแสดง (1-5)"New value: +"Number of sutta-context examples to include (1-5)."
    • changedInput schema / properties / word / description
      Previous value: -"คำที่ต้องการค้นหา (เช่น \"dukkha\", \"กฐิน\")"New value: +"Word to look up (e.g. \"dukkha\", \"กฐิน\")."
  3. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Goes well past the annotations by disclosing non-obvious behavior: Thai entries are always returned even when ENABLED_LANGUAGES disables Thai, context examples are randomly sampled so two identical calls differ, and related_words are substring matches that surface opposites like adhamma. The random-sampling note sits slightly awkwardly beside idempotentHint=true, but that hint concerns side effects, not output determinism, so this is context rather than contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose, but the middle section is padded: the full Thai title of the Payutto dictionary and the emoji-headed "About the dictionary sources" block take more space than the actionable point (Thai entries are always available) requires. Several payload-structure sentences duplicate what the output schema already conveys.

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?

An output schema exists, so return values need not be explained, and the description still covers the two behaviors an agent would otherwise get wrong: always-on Thai entries and randomized context. The main omission is routing relative to the more than a dozen sibling tools.

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 already documents word, language, and limit_context, giving a baseline of 3. The description adds no syntax or format detail for any parameter beyond noting that Thai content survives a language filter, which is behavioral rather than parameter-level information.

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+resource ("Look up the dictionary meaning of a Pāli word") plus scope ("with sutta context"). The line that definitions "come from the dictionaries, not the canon" implicitly distinguishes it from the sibling define_from_suttas, though that sibling is never 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 Guidelines3/5

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

Usage is implied rather than stated: the agent can infer “use this for lexicon entries, pair with context,” and there is a helpful directive that the AI client should translate Thai entries itself. However there is no explicit when-to-use / when-not-to-use guidance and no routing instruction versus define_from_suttas, parse_pali_word, or get_reference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources