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

dictcc_search

Search dict.cc headwords by prefix or substring across supported language pairs and return matches in dict.cc ranking order, with an optional result limit.

Instructions

Find dict.cc headwords containing a query (prefix or substring), in dict.cc's own ranking order. query: e.g. Hau, Haus. pair: de-en (default) or any supported pair (see dictcc_translate). 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_search"
  }
}

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

A3.9/5.0

Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose result ordering (dict.cc ranking) and a hard result cap, which are useful behavioral facts. It says nothing about what happens with zero matches, whether results are paginated, or any rate/auth constraints, and the 'prefix or substring' phrasing leaves ambiguous which mode actually applies to a given query.

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?

Three short lines, front-loaded with the core purpose, then the parameters in the order an agent needs them. The mid-sentence line breaks are slightly awkward but nothing is redundant or padding.

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 three-parameter, one-required read tool with no annotations, the definition covers purpose, matching mode, ordering, and every parameter's constraints, and an output schema exists so return values need not be described. Only edge behavior (no results, pagination, pair enumeration) is left uncovered.

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%, so the description must compensate, and it does: query gets worked examples (Hau, Haus), pair gets a default and a pointer to the sibling for valid values, and limit gets an explicit 1..50 range plus default 10. The only shortfall is that valid pair values must be looked up elsewhere and there is no parameter controlling prefix vs substring matching.

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?

States a specific verb and resource — find dict.cc headwords — and pins down the matching semantics ('prefix or substring') plus the ordering ('dict.cc's own ranking order'). That is enough for an agent to tell it apart from dictcc_translate, which resolves a word rather than listing candidate headwords.

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 rather than stated: the substring/headword framing suggests autocomplete-style lookup, and the pair note points at dictcc_translate for the list of supported pairs. There is no explicit 'use this when…, use dictcc_translate when…' routing statement or exclusion.

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

Deploy Server