io.github.mohammad-abbasi-sh/dictcc-mcp

dictcc_translate

Translate words or phrases across 23 language pairs via dict.cc, returning word class, gender, usage notes, and community vote rankings.

Instructions

Translate a word or phrase with dict.cc: translations with word class, gender, usage notes and community votes. query: e.g. Haus, laufen, house. pair: de-en (default), de-el, de-eo, de-es, de-fi, de-fr, de-hr, de-hu, de-is, de-it, de-la, de-nl, de-no, de-pl, de-pt, de-ro, de-ru, de-sk, de-sq, de-sr, de-sv, de-tr, de-uk. limit: 1..50 (default 10).

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": {
      "query": "<query>"
    },
    "name": "dictcc_translate"
  }
}

Input Schema

Name	Required	Default
`pair`	No	de-en
`limit`	No
`query`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

A4/5.0

Behavior4/5

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

No annotations exist, so the description carries the burden and it does disclose the meaningful behavior: results include word class, gender, usage notes and community votes, which signals data quality and format. It omits edge behavior such as what happens when no translation is found or whether lookups are rate-limited, but for a non-mutating dictionary lookup this is a solid disclosure.

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 core purpose is front-loaded in the first sentence, with parameter notes following in compact shorthand. The long pair enumeration is bulky but justified because the schema carries no enum or description, so every listed value does work.

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?

With an output schema present, return values need not be explained, and all three parameters are documented in the text. The remaining gap is behavioral edge cases — empty results, pagination beyond limit, or lookup failures — which are not addressed.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate and it does fully: query is illustrated with both German and English examples, pair enumerates the accepted values with the default (de-en), and limit states the 1..50 range with default 10. All three parameters gain meaning beyond the bare typed schema.

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 uses a specific verb and resource — 'Translate a word or phrase with dict.cc' — and even previews the result shape (word class, gender, usage notes, community votes). It does not explicitly distinguish itself from the sibling dictcc_search, leaving the translate-vs-search split to inference.

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 implied by 'translate a word or phrase' plus concrete query examples (Haus, laufen, house), which tells an agent this handles both German and English lookups. There is no explicit when-to-use guidance or statement of when dictcc_search would be the better choice.

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

Deploy Server