SilaLingo Thai Dictionary

Get Thai Sign

get_sign

Read-onlyIdempotent

Get a real Thai street sign with transcription and translation.

``sign_ref`` is a numeric sign ID or a URL slug. Returns the title,
location, full Thai text, romanization, translation, difficulty, tags,
annotated text regions (each with its own translation) and the photo URL.

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": {
      "sign_ref": "<sign_ref>"
    },
    "name": "get_sign"
  }
}

Input Schema

Name	Required	Description	Default
`sign_ref`	Yes

Output Schema

Name	Required	Description
`id`	Yes
`url`	Yes
`slug`	Yes
`tags`	No
`title`	Yes
`regions`	No	Annotated text regions with translations
`location`	No	Where the sign was photographed, e.g. 'Chatuchak Market'
`image_url`	No
`thai_text`	No
`description`	No
`translation`	No
`romanization`	No
`difficulty_level`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.6/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 the safety profile is covered. The description adds a useful enumeration of what comes back (regions, translations, photo URL), but it says nothing about failure behavior for an invalid ID/slug or lookup limits, so it is additive without being rich.

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 sentences, front-loaded with the purpose and followed by the parameter contract and return contents; nothing is redundant. Minor deductions for the doubled-backtick markup around sign_ref and the long comma-separated field list, which is dense rather than elegantly structured.

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 tool with annotations and an output schema, the description covers purpose, the dual ID/slug input form, and the shape of the result. Remaining gaps (error handling, whether slug is case-sensitive, example values) are modest at this complexity level.

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 single parameter has no description in the schema, so the description must carry the load — and it does, explaining that sign_ref is either a numeric sign ID or a URL slug. That resolves a genuine ambiguity, though no slug examples or format rules are given.

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?

The description opens with a concrete verb+resource: 'Get a real Thai street sign with transcription and translation.' That is unambiguous and clearly distinct from the sibling tools (dictionary, tones, letters, sentence details). It stops short of explicitly differentiating itself from those siblings, so it lands at 4 rather than 5.

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 only implied by the resource type — an agent can infer this is the tool for fetching a specific sign, but the description never states when to use it versus the other lookup tools, nor any preconditions. There are no exclusions or 'use X instead' routing cues.

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?