Skip to main content
Glama
Sign In
urbandictmcp

urbandictmcp

by qramarq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

urban_dictionary_defid

Retrieve a specific Urban Dictionary definition using its unique definition ID. Access crowdsourced content directly by ID.

Instructions

Fetch an Urban Dictionary definition by definition ID. 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": {
      "defid": "<defid>"
    },
    "name": "urban_dictionary_defid"
  }
}

Input Schema

NameRequiredDescriptionDefault
defidYesUrban Dictionary definition ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Warns that results are crowdsourced and may contain explicit language. No annotations exist, so description carries burden. Could disclose that it's a read-only operation or mention data freshness.

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?

Two concise sentences with front-loaded action and important warning. No wasted words.

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

Completeness4/5

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

Adequate for a simple fetch tool with one parameter. Warns about content, but could hint at return structure (e.g., 'returns definition text and examples').

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% with a clear description. Description adds no additional parameter context beyond what schema provides.

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?

Clear verb ('Fetch') and resource ('definition') with explicit method ('by definition ID'). Distinct from sibling tools that fetch by word or random.

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

Usage Guidelines3/5

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

Implies usage when definition ID is known, but lacks explicit guidance on when to use this over siblings (e.g., 'use this if you have the ID, otherwise use define').

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