Skip to main content
Glama
Sign In
DialectOS

DialectOS

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

translate_text

Translate text into a specific Spanish dialect by selecting the regional variant, translation provider, and formality level.

Instructions

Translate text to a Spanish dialect

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": {
      "text": "<text>"
    },
    "name": "translate_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to translate
formalNoUse formal tone
dialectNoSpanish dialect code (e.g., es-ES, es-MX, es-AR)
informalNoUse informal tone
providerNoTranslation provider name (deepl, libre, mymemory)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits such as idempotency, permissions, or side effects. For a translation tool, at minimum it should indicate it returns translated text.

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?

Single sentence, concise and front-loaded. Efficient, though could be slightly more informative without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Description is too brief given 5 parameters and many siblings. It does not explain dialect limitations, the relationship between formal/informal, or the response structure (no output schema).

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

Parameters3/5

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

Schema coverage is 100%, so baseline is 3. The description adds no meaning beyond the schema's parameter descriptions; it only restates the tool's purpose.

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 uses specific verb 'Translate' and resource 'text', explicitly limiting to Spanish dialects. This clearly distinguishes from sibling tools like detect_dialect or list_dialects.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus siblings like batch_translate_locales or check_formality. The description lacks any context about alternatives or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools