Longman Dictionary MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| get_dictionary_entryC | Busca o HTML do Longman para uma palavra e retorna JSON parseado (dictionaryEntries, simpleForm, continuousForm) |
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 ambiguity or overlap between tools. The tool's purpose is clearly defined as fetching and parsing dictionary entries from Longman.
Since there is only a single tool, naming consistency is inherently perfect. The tool name 'get_dictionary_entry' follows a clear verb_noun pattern, which would be consistent if more tools were added.
A single tool is too few for a dictionary server, as it lacks basic operations like searching for words, handling synonyms/antonyms, or managing user history. This minimal scope limits functionality and feels incomplete for the domain.
The tool surface is severely incomplete for a dictionary server. While it provides entry retrieval, it misses essential features such as word search, phonetic lookups, example sentences, or related terms, which are standard in dictionary applications.