Skip to main content
Glama
Sign In
DialectOS

DialectOS

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_bilingual_doc

Translate a markdown file into a side-by-side bilingual document with original and translated sections, supporting multiple Spanish dialects.

Instructions

Create a side-by-side bilingual document with original and translated sections

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": {
      "filePath": "<filePath>"
    },
    "name": "create_bilingual_doc"
  }
}

Input Schema

NameRequiredDescriptionDefault
dialectNoSpanish dialect code (e.g., es-ES, es-MX, es-AR)
filePathYesPath to the markdown file to translate
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 fails to disclose behavioral traits such as whether it overwrites files, needs authentication, or has rate limits, leaving the agent uninformed about side effects.

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?

The description is a single sentence with no wasted words, but slightly more context (e.g., output format) could improve utility without harming conciseness.

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?

For a tool that creates files, missing details on output naming, file overwriting behavior, and error handling make it incomplete given no output schema or annotations.

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 the description adds minimal value beyond the parameter names and types; it does not clarify how dialect or provider affect the output.

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 clearly states the tool creates a side-by-side bilingual document with original and translated sections, which is distinct from sibling tools like translate_markdown or translate_text.

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 alternatives like translate_markdown or batch_translate_locales, nor any mention of prerequisites 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