SilaLingo Thai Dictionary

Get Thai Sentence Details

get_sentence_details

Read-onlyIdempotent

Get a verified Thai sentence with a word-by-word breakdown.

``sentence_id`` is a numeric ID from search_thai_dictionary. Returns the
Thai text, romanization, natural and literal translations, formality,
per-word breakdown (Thai, romanization, meaning, tones) and audio URLs.

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": {
      "sentence_id": "<sentence_id>"
    },
    "name": "get_sentence_details"
  }
}

Input Schema

Name	Required	Description	Default
`sentence_id`	Yes

Output Schema

Name	Required	Description
`id`	Yes
`url`	Yes
`thai`	Yes
`words`	No	Word-by-word breakdown, in order
`audio_url`	No
`translation`	Yes	Natural English translation
`context_note`	No
`romanization`	Yes
`sentence_type`	No
`audio_slow_url`	No
`formality_level`	No
`difficulty_level`	No
`literal_translation`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and a closed world, so the safety profile is covered. The description adds non-obvious context beyond that: the sentence is 'verified' (a data-quality guarantee) and the payload includes romanization, natural vs literal translation, formality and audio URLs. Some of that overlaps the output schema, keeping it below 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.

Conciseness4/5

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

Two short sentences, front-loaded with purpose and then the parameter provenance; every clause is relevant. The return-value enumeration is somewhat list-like and partially duplicates the output schema, which costs a point.

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 tool with a full output schema and rich annotations, the description supplies the two things structured fields cannot: where the ID comes from and what the sentence record contains. Nothing essential for correct invocation is missing.

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 says 'integer', so the description does the real work: it establishes that sentence_id is numeric and must be sourced from search_thai_dictionary rather than invented or taken from a word result. It does not give format or range details, preventing a 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?

The description opens with a specific verb and resource ('Get a verified Thai sentence') plus the distinctive scope 'word-by-word breakdown', which clearly separates it from get_word_details and search_thai_dictionary. An agent can pick this 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?

It states where the required argument comes from ('sentence_id is a numeric ID from search_thai_dictionary'), giving a concrete entry path, but it does not state when NOT to use it or contrast against get_word_details for single-word lookups.

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?