Dictionary By Api Ninjas
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API key for Dictionary By Api Ninjas API |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| v1dictionaryC | API Ninjas Dictionary API endpoint. |
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
Only one tool exists, so there is no ambiguity in tool selection. The single tool has a clearly distinct purpose as a dictionary lookup endpoint.
With only one tool, naming is inherently consistent. The name 'v1dictionary' follows a reasonable pattern of version prefix and resource name.
A single dictionary lookup tool is appropriate for the server's intended scope. Many dictionary APIs expose only one endpoint, so the count is well-scoped.
The single tool likely covers basic dictionary lookups, but may lack additional features like synonyms or examples. However, for a minimal dictionary service, it is reasonably complete.