urbandictmcp
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| urban_dictionary_defineB | Look up definitions for a term on Urban Dictionary. Results are crowdsourced and may contain explicit or offensive language. |
| urban_dictionary_randomA | Fetch random Urban Dictionary definitions. Results are crowdsourced and may contain explicit or offensive language. |
| urban_dictionary_defidA | Fetch an Urban Dictionary definition by definition ID. Results are crowdsourced and may contain explicit or offensive language. |
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 retrieval method: by definition ID, by term, and random. No overlap in functionality.
All tools follow a consistent `urban_dictionary_<operation>` pattern with lowercase underscore separation.
Three tools cover the essential operations for an Urban Dictionary server: lookup by term, by ID, and random. This is well-scoped for the domain.
The core search and retrieval operations are covered. Minor gaps like trending or user contributions exist but are not critical for basic usage.