Skip to main content
Glama
Sign In
urbandictmcp

urbandictmcp

by qramarq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

urban_dictionary_define

Look up definitions for a word or phrase from Urban Dictionary, with options to limit results and sort by votes or recency.

Instructions

Look up definitions for a term on Urban Dictionary. Results are crowdsourced and may contain explicit or offensive language.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "term": "<term>"
    },
    "name": "urban_dictionary_define"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYesThe word or phrase to define.
limitNoMaximum number of definitions to return.
sort_byNoSort definitions by vote score, newest written date, or the API's original order.top

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description discloses the crowdsourced and potentially offensive nature of results, which is a behavioral trait. However, it omits details about authentication, rate limits, error handling (e.g., term not found), or that results are paginated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with no fluff. Every sentence serves a purpose: stating function and issuing a content warning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema, the description does not describe what the return value contains (e.g., list of definitions with fields like word, definition, example). It is insufficient for an agent to fully understand the tool's behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds no extra meaning beyond the schema's parameter descriptions, so it neither helps nor hinders.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (look up definitions) and the resource (a term on Urban Dictionary). It distinguishes from sibling tools (defid and random) implicitly by focusing on term lookup, making the purpose specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives (e.g., defid for specific ID, random for random term). The warning about explicit content is not a usage guideline. Agent lacks context for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools