SilaLingo Thai Dictionary

Get Thai Letter

get_letter

Read-onlyIdempotent

Get one Thai alphabet letter's full details.

``letter_ref`` is a numeric letter ID, a URL slug, or the exact Thai
glyph (e.g. "ก"). Returns the glyph, English and Thai names, letter type
(consonant/vowel/tone mark/special), consonant class for consonants,
romanization, IPA, a description, the associated memory word, audio and a
stroke-order animation URL, plus its silalingo.com page.

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": {
      "letter_ref": "<letter_ref>"
    },
    "name": "get_letter"
  }
}

Input Schema

Name	Required	Description	Default
`letter_ref`	Yes

Output Schema

Name	Required	Description
`id`	Yes
`url`	Yes
`name`	Yes	English name, e.g. 'Ko Kai'
`thai`	Yes	The letter glyph, e.g. 'ก'
`audio_url`	No
`name_thai`	No
`description`	No
`letter_type`	Yes	consonant / vowel / tone_mark / special
`phonetic_ipa`	No
`romanization`	No
`associated_word`	No	The word used to remember the letter, e.g. 'chicken'
`consonant_class`	No	mid / high / low for consonants, empty otherwise
`stroke_order_url`	No	Lottie stroke-order animation, when available
`pronunciation_guide`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, and closed-world, so the safety profile is covered. The description adds that a letter ref may be an ID, slug, or raw glyph and that the response includes a silalingo.com page link, but it says nothing about failure behavior when the glyph does not exist or is ambiguous.

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 verb+resource sentence, then a parameter paragraph, then a return-value paragraph. Efficient and easy to scan, though the itemized return list is somewhat verbose given an output schema already exists.

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 one-parameter read-only lookup with annotations and an output schema, this covers purpose, input formats, and payload shape. Only edge-case behavior (unknown glyph, ambiguous slug) is left out, which is a minor gap rather than a blocking one.

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

Parameters5/5

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

Schema coverage is 0% and the single parameter is described only as 'Letter Ref', so the description carries the full burden — and it does: it enumerates the three accepted forms (numeric ID, URL slug, exact Thai glyph) with a concrete example, which is exactly what an agent needs to build a valid call.

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: retrieving one Thai alphabet letter's full details. The scope (single letter, not word or sentence) is clear enough to distinguish it from get_word_details and get_sentence_details, though it never names those siblings 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 by 'Get one ... letter's full details' — the agent can infer it is the detail lookup for a single letter — but there is no explicit when-to-use/when-not guidance and no alternative tool is named for adjacent needs like tone explanations or dictionary search.

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?