Lookup-Modern-Chinese-Dictionary
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XBY_APIKEY | Yes | 你的实际apikey (Your actual API key) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookup_wordC | 查单词 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
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.
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.
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.
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.