Skip to main content
Glama
Sign In
DialectOS

DialectOS

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

translate_api_docs

Translate API documentation markdown files into regional Spanish dialects, preserving tables and lists.

Instructions

Translate API documentation markdown with optimized handling for tables and lists

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": "translate_api_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
dialectNoSpanish dialect code (e.g., es-ES, es-MX, es-AR)
filePathYesPath to the API documentation markdown file
providerNoTranslation provider name (deepl, libre, mymemory)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden but only mentions 'optimized handling' without detailing behavioral traits like idempotency, speed, or output format. It lacks essential context for a translation tool.

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?

A single, concise sentence that directly states the tool's purpose and key feature without extraneous text.

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?

Given no output schema and multiple siblings, the description lacks completeness. It does not explain what happens with tables/lists, error handling, or how to interpret results.

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 baseline is 3. The description adds no parameter-specific meaning beyond what the schema already provides.

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 'translate API documentation markdown' as the action and resource, and highlights optimized handling for tables and lists, distinguishing it from sibling tools like translate_markdown.

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?

The description implies usage for API documentation with tables/lists via 'optimized handling', but provides no explicit guidance on when to use this over siblings like translate_markdown or translate_text.

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