SilaLingo Thai Dictionary

Search Thai Dictionary

search_thai_dictionary

Read-onlyIdempotent

Search SilaLingo's verified Thai dictionary.

The query may be Thai script, romanization, or English. ``type`` is one of
"all", "word", "sentence", "letter" (default "all"). ``limit`` caps
results per type (default 10, max 50). Returns compact hits with Thai,
romanization, definition and a silalingo.com URL; call get_word_details
or get_sentence_details with a hit's ID for the full entry.

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": {
      "query": "<query>"
    },
    "name": "search_thai_dictionary"
  }
}

Input Schema

Name	Required	Default
`type`	No	all
`limit`	No
`query`	Yes

Output Schema

Name	Required	Description
`query`	Yes
`total`	Yes	Total matches across the requested types
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds useful context beyond them: results are 'compact hits' rather than full entries, and each carries a silalingo.com URL. Auth or rate-limit behavior is not mentioned, keeping it short of a 5.

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

Conciseness5/5

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

Three tight sentences, front-loaded with purpose, then parameters, then follow-up routing. Nothing is redundant apart from repeating the documented default for type, which is acceptable for readability.

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?

Although an output schema exists, the description still summarizes the hit shape (Thai, romanization, definition, URL) and explains the ID-based handoff to detail tools. For a three-parameter read-only search, nothing an agent needs to invoke 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 schema declares no enum for 'type', so the description carries the full burden: it defines the accepted query formats, lists all four type values, and supplies the default and max for limit. This is exactly the compensation the schema requires.

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 plus resource ('Search SilaLingo's verified Thai dictionary') and names the sibling tools (get_word_details, get_sentence_details) reserved for full entries, so an agent can distinguish it from the detail lookups immediately.

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?

Explains accepted query forms (Thai script, romanization, English), enumerates the type values with a default, and gives an explicit routing rule: take a hit's ID to the detail tools for the full entry. When-to-use and the alternative are both stated.

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?