arabic-dict-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_AUTH_TOKEN | No | Bearer token required when running the server in HTTP mode. The server refuses to start over HTTP without this token set. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookup_rootA | Look up an Arabic root and return all dictionary entries under it. Accepts a root in any form: "كتب", "ك ت ب", "ك-ت-ب", or with diacritics like "كَتَبَ". Diacritics and letter-variants (ا/أ/إ/آ, ي/ى, ه/ة) are normalized before matching. Use this when the user has already identified the root or when you want to see all sibling words for a lemma. Returns entries from three sources:
All returned Arabic words are fully vocalized (tashkeel is preserved from the source, including final case marks) so the caller can tell homographs apart. Input is diacritic-insensitive; output is not. |
| lookup_wordA | Look up a surface Arabic word (any inflected form or lemma). Returns matching entries, each labelled with its root — pivot to
|
| search_meaningA | Full-text search over dictionary meanings. Use when the user asks "what's the Arabic root for X?" or gives a concept
in English or Arabic. |
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 3 tools
Each tool targets a distinct access path: root lookup, surface word lookup, and meaning search. The descriptions explicitly differentiate when to use each, so there is no ambiguity.
All tools follow a clear verb_noun pattern: lookup_root, lookup_word, search_meaning. The pattern is consistent and predictable.
Three tools is well-scoped for a dictionary server. Each tool covers a necessary and non-overlapping function, and the count is within the typical 3-15 range.
The tool set covers the full spectrum of dictionary queries: root lookup, word lookup, and semantic search. This provides comprehensive coverage for the domain with no obvious dead ends.