SilaLingo Thai Dictionary

Explain Thai Tones

explain_thai_tones

Read-onlyIdempotent

Explain the Thai tone system with verified rules and audio examples.

Pass a tone name in ``topic`` (mid, low, falling, high, rising) for one
tone, or omit it for the full guide: all five tones with contour
descriptions and examples, the complete tone-determination matrix
(consonant class x syllable ending x tone mark), consonant class counts,
and a same-syllable 5-tone comparison set. Use this whenever a user asks
why a Thai word has a particular tone.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "explain_thai_tones"
  }
}

Input Schema

Name	Required	Description	Default
`topic`	No

Output Schema

Name	Required	Description
`url`	Yes	Interactive tone-rules page on silalingo.com
`tones`	Yes
`comparison`	No	One syllable pronounced with all 5 tones for ear training
`rules_matrix`	No	The full tone-determination matrix: keys are '<consonant class> / <syllable ending>', values map tone-mark name to the resulting tone. Attested combinations only.
`rules_summary`	Yes	How written Thai determines the spoken tone
`consonant_classes`	No	How many Thai consonants belong to each class (mid/high/low) — the class is the primary input to the tone rules

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly/ idempotent/ closed-world, so the safety profile is covered. The description adds real behavioral value by previewing exactly what the full guide returns (matrix, class counts, 5-tone comparison set) and what the single-tone mode returns, which goes beyond the structured fields.

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 statement of purpose, then parameter behavior, then usage trigger. The inventory of full-guide contents is a long clause but every item informs the agent's choice between the two modes, leaving little genuine waste.

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?

For a one-parameter, read-only reference tool with an output schema already documenting return structure, the description covers purpose, parameter values, default behavior, and usage trigger. Nothing needed to call it correctly is missing.

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 topic parameter has no enum in the schema, so the description carries the full burden — and does: it enumerates the accepted values (mid, low, falling, high, rising) and defines the omit/null default as 'full guide'. That is exactly the missing meaning.

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 and resource ('Explain the Thai tone system with verified rules and audio examples') and the content differs sharply from the sibling lookup tools (dictionary search, letter, sign, sentence/word details). An agent can tell it is the tone-reference tool without opening the 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?

Gives an explicit trigger: 'Use this whenever a user asks why a Thai word has a particular tone,' and explains the two invocation modes (single tone via topic, or omit for the full guide). It stops short of naming a sibling alternative or stating when NOT to use it, so not 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?