Skip to main content
Glama
io.github.mohammad-abbasi-sh/dictcc-mcp

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

dictcc_health

Checks whether dict.cc is reachable now and returns ok, blocked, or error status with the HTTP code and probed URL, so you can detect bot walls or rate limits before searching.

Instructions

Check whether dict.cc is reachable right now.

Returns status ok (HTTP 200), blocked (HTTP 403/429 — bot wall or rate limit) or error, plus the HTTP status and the probed URL. One polite request; it does not fetch any listings.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dictcc_health"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it enumerates the three outcome states with their HTTP meanings (200 / 403-429 bot wall or rate limit / error), discloses that it makes exactly one request, and explicitly bounds the side effect by saying no listings are fetched. What is missing is any note on latency, caching, or whether a "blocked" result is transient.

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?

Three short sentences, front-loaded with the core question, then the return contract, then the side-effect reassurance. No filler and no repetition of the tool name.

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

Completeness5/5

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

For a no-argument health probe this is fully sufficient: the agent knows what it asks, what comes back, and that the call is cheap and non-invasive. An output schema exists, so the description's brief recap of the status values is a bonus rather than a necessity.

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?

The tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. It correctly avoids inventing parameter discussion and instead spends its words on outcomes.

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 ("Check whether dict.cc is reachable") with explicit temporal scope ("right now"). The closing clause "it does not fetch any listings" implicitly separates it from the search/translate siblings, so an agent can tell it is a liveness probe rather than a data tool.

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: an agent can infer this is a pre-flight or failure-diagnosis check, but the description never says when to call it (before searching? after an error?) or when not to bother. No alternative is named, so the agent must infer the routing itself.

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