Skip to main content
Glama
xiaobenyang-com

Lookup-Modern-Chinese-Dictionary

by xiaobenyang-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

查现代汉语词典 Lookup Modern Chinese Dictionary

从现代汉语词典中检索单词释义，为用户提供便捷的词典查询服务。 Search for word definitions from modern Chinese dictionaries to provide users with convenient dictionary query services.## 工具列表 Tool List

本MCP服务封装下列工具，可让模型通过标准化接口调用以下功能。 本MCP服务封装下列工具，可让模型通过标准化接口调用以下功能。

工具 Tool

描述 Description

lookup_word

查单词

检查服务 ## Inspector

工具在线测试： https://mcp.xiaobenyang.com/inspector/1809126168192010

Online Tool test https://mcp.xiaobenyang.com/inspector/1809126168192010

Related MCP server: Cambridge Dictionary MCP Server

服务配置 MCP Server Config

如何获取 XBY-APIKEY ？ How to get XBY-APIKEY ?

访问小笨羊科技网站 https://xiaobenyang.com，注册用户即可获得APIKEY Visit XiaoBenYang website https://xiaobenyang.com, register and get the APIKEY.

SSE

{
  "mcpServers": {
    "查现代汉语词典": {
      "headers": {
        "XBY-APIKEY": "<YOUR_XBY_APIKEY>"
      },
      "type": "sse",
      "url": "https://mcp.xiaobenyang.com/1809126168192010/sse"
    }
  }
}

STREAMABLE HTTP

{
  "mcpServers": {
    "查现代汉语词典": {
      "headers": {
        "XBY-APIKEY": "<YOUR_XBY_APIKEY>"
      },
      "type": "streamable_http",
      "url": "https://mcp.xiaobenyang.com/1809126168192010/mcp"
    }
  }
}

STDIO

{
    "mcpServers": {
        "查现代汉语词典": {
          "command": "npx",
          "args": [
            "-y",
            "xiaobenyang-mcp"
          ],
          "env": {
            "XBY_APIKEY": "<YOUR_XBY_APIKEY>",
            "mcpId": "1809126168192010",
          },
          "transport": "stdio"
        }
      }
}

Available Tools

1 tool
lookup_wordlookup_wordC

查单词

ParametersJSON Schema
NameRequiredDescriptionDefault
wordYes

TDQS

C2/5.0
Behavior1/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. '查单词' only indicates a lookup action without describing what the tool returns, whether it requires authentication, rate limits, error conditions, or any behavioral traits. This is inadequate for a tool with zero annotation coverage.

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?

The description is extremely concise at just two characters. It's front-loaded with the core action, though this brevity comes at the cost of completeness rather than being efficiently informative.

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

Completeness1/5

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

Given no annotations, no output schema, and 0% schema description coverage, the description is completely inadequate. It doesn't explain what the tool does beyond the name, what it returns, or how to use the parameter. This leaves the agent with insufficient information to use the tool effectively.

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

Parameters2/5

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

The schema has 1 parameter with 0% description coverage. The description doesn't mention the 'word' parameter at all, providing no semantic context beyond what's implied by the tool name. It fails to compensate for the schema's lack of parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description '查单词' (look up a word) restates the tool name 'lookup_word' in Chinese, making it tautological. It specifies the verb 'look up' and resource 'word', but doesn't provide any additional context about what kind of lookup this is (dictionary, translation, definition, etc.).

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?

There are no explicit guidelines about when to use this tool. The description doesn't mention any prerequisites, alternatives, or specific contexts. With no sibling tools, the lack of guidance is less critical but still leaves the agent without usage context.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • First observedlookup_word
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

C2.5/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined as looking up words in a dictionary, making it completely distinct by default.

Naming Consistency5/5

A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The tool name 'lookup_word' follows a clear verb_noun pattern, which would be consistent if more tools were added.

Tool Count2/5

A single tool for a dictionary server feels thin and under-scoped. While a basic lookup function is essential, typical dictionary services might include additional operations like searching by definition, getting synonyms, or handling multiple languages, making one tool insufficient for comprehensive coverage.

Completeness2/5

The tool surface is severely incomplete for a dictionary domain. It only provides word lookup, missing obvious functionalities such as searching for words by meaning, getting pronunciation, examples, or related terms. This will likely cause agent failures when more complex queries are needed.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers