SilaLingo Thai Dictionary

Get Thai Word Details

get_word_details

Read-onlyIdempotent

Get the full verified dictionary entry for one Thai word.

Accepts a numeric word ID (from search_thai_dictionary), a URL slug, or
the exact Thai text. Returns romanization, IPA, tone transcription,
per-syllable tones, syllable breakdown, classifier, part of speech,
usage/cultural notes, audio URLs, related words/synonyms/antonyms and
example sentences — everything needed to answer "how do I say X in Thai"
accurately.

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_id_or_slug": "<word_id_or_slug>"
    },
    "name": "get_word_details"
  }
}

Input Schema

Name	Required	Description	Default
`word_id_or_slug`	Yes

Output Schema

Name	Required	Description
`id`	Yes
`url`	Yes
`slug`	Yes
`thai`	Yes
`tones`	No	Tone per syllable: mid/low/falling/high/rising
`antonyms`	No
`meanings`	No	Every sense of the word, primary first
`synonyms`	No
`audio_url`	No
`classifier`	No	Thai classifier for counting this noun, if any
`definition`	Yes
`usage_notes`	No
`phonetic_ipa`	No
`romanization`	Yes
`cultural_note`	No
`related_words`	No
`audio_slow_url`	No
`part_of_speech`	No
`frequency_level`	No
`difficulty_level`	No
`example_sentences`	No
`syllable_breakdown`	No	Thai syllables, e.g. ['สวัส', 'ดี']
`tone_transcription`	No	Tone-marked pronunciation, e.g. 'sà-wàt-dii' (hyphenated syllables)
`definition_extended`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety and retry behavior are covered. The description adds only "verified" and a field inventory that the output schema already supplies; it discloses nothing about rate limits, caching, or behavior when a word is not found.

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?

Front-loaded with the core action, then input forms, then returned data — a sensible order with no filler sentences. The long enumeration of return fields is partly redundant with the output schema and could be trimmed.

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 single-parameter read-only lookup with a real output schema and covering annotations, the description supplies everything needed to call it correctly, including the input-form flexibility and provenance of the ID. Missing only edge-case behavior such as what happens on an unknown or ambiguous word.

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?

Schema coverage is 0% and the schema only names the field "word_id_or_slug" as a plain string, so the description carries real weight by disclosing that numeric word ID, URL slug, or exact Thai text are all acceptable. It does not explain precedence or format rules when the input is ambiguous, keeping it below 5.

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?

States a specific verb+resource ("Get the full verified dictionary entry for one Thai word") and differentiates itself from search_thai_dictionary by framing this as the detail lookup reached from search results. An agent can distinguish it from get_sentence_details or get_letter without reading any schema.

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?

Implies the workflow clearly: the ID comes from search_thai_dictionary, so search-then-detail is the intended path, and the "how do I say X in Thai" framing names the use case. No explicit when-not guidance or mention of get_sentence_details as the sentence-level alternative, so it stops short of a 5.

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

All SilaLingo Thai Dictionary tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?