Skip to main content
Glama
karanb192

Reddit Buddy MCP

by karanb192

reddit_explain

Explains Reddit terms, slang, and culture by providing definitions, origins, usage examples, and context for better understanding of the platform.

Instructions

Get explanations of Reddit terms, slang, and culture. Returns definition, origin, usage, and examples.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesReddit term to explain (e.g., "karma", "cake day", "AMA", "ELI5")

Implementation Reference

  • The main handler function for the 'reddit_explain' tool. It provides explanations for common Reddit terms using a predefined dictionary, returning structured data with definition, origin, usage, and examples.
    async redditExplain(params: z.infer<typeof redditExplainSchema>) {
      // This would ideally use a knowledge base, but we'll provide common explanations
      const explanations: Record<string, any> = {
        'karma': {
          definition: 'Reddit points earned from upvotes on posts and comments',
          origin: 'Concept from Hinduism/Buddhism adapted for Reddit\'s scoring system',
          usage: 'Users accumulate karma to show contribution quality',
          examples: ['High karma users are often trusted more', 'Some subreddits require minimum karma to post'],
        },
        'cake day': {
          definition: 'Anniversary of when a user joined Reddit',
          origin: 'Reddit displays a cake icon next to usernames on this day',
          usage: 'Users often get extra upvotes on their cake day',
          examples: ['Happy cake day!', 'It\'s my cake day, AMA'],
        },
        'ama': {
          definition: 'Ask Me Anything - Q&A session with interesting people',
          origin: 'Started in r/IAmA subreddit',
          usage: 'Celebrities, experts, or people with unique experiences answer questions',
          examples: ['I am Elon Musk, AMA', 'I survived a plane crash, AMA'],
        },
        'eli5': {
          definition: 'Explain Like I\'m 5 - request for simple explanation',
          origin: 'From r/explainlikeimfive subreddit',
          usage: 'Used when asking for complex topics to be explained simply',
          examples: ['ELI5: How does bitcoin work?', 'Can someone ELI5 quantum computing?'],
        },
        'til': {
          definition: 'Today I Learned - sharing interesting facts',
          origin: 'From r/todayilearned subreddit',
          usage: 'Prefix for sharing newly discovered information',
          examples: ['TIL bananas are berries', 'TIL about the Baader-Meinhof phenomenon'],
        },
        'op': {
          definition: 'Original Poster - person who created the post',
          origin: 'Common internet forum terminology',
          usage: 'Refers to the person who started the discussion',
          examples: ['OP delivers!', 'Waiting for OP to respond'],
        },
        'repost': {
          definition: 'Content that has been posted before',
          origin: 'Common issue on content aggregation sites',
          usage: 'Often called out by users who\'ve seen the content before',
          examples: ['This is a repost from last week', 'General Reposti!'],
        },
        'brigading': {
          definition: 'Coordinated effort to manipulate votes or harass',
          origin: 'Named after military brigade tactics',
          usage: 'Against Reddit rules, can result in bans',
          examples: ['Don\'t brigade other subs', 'This looks like brigading'],
        },
        '/s': {
          definition: 'Sarcasm indicator',
          origin: 'HTML-style closing tag for sarcasm',
          usage: 'Added to end of sarcastic comments to avoid misunderstanding',
          examples: ['Yeah, that\'s totally going to work /s', 'Great idea /s'],
        },
        'banana for scale': {
          definition: 'Using a banana to show size in photos',
          origin: 'Started as a Reddit meme in 2013',
          usage: 'Humorous way to provide size reference',
          examples: ['Found this rock, banana for scale', 'No banana for scale?'],
        },
      };
    
      const term = params.term.toLowerCase();
      const explanation = explanations[term];
    
      if (!explanation) {
        return {
          definition: 'Term not found in database. This might be a subreddit-specific term or newer slang.',
          origin: 'Unknown',
          usage: 'Try searching Reddit for this term to see how it\'s used',
          examples: [],
          relatedTerms: [],
        };
      }
    
      return {
        definition: explanation.definition,
        origin: explanation.origin,
        usage: explanation.usage,
        examples: explanation.examples,
        relatedTerms: [],
      };
    }
  • Zod schema defining the input parameters for the reddit_explain tool: a single 'term' string.
    export const redditExplainSchema = z.object({
      term: z.string().describe('Reddit term to explain (e.g., "karma", "cake day", "AMA")'),
    });
  • Registers the 'reddit_explain' tool in the MCP server by defining its name, description, and input schema in the toolDefinitions array.
    {
      name: 'reddit_explain',
      description: 'Get explanations of Reddit terms, slang, and culture. Returns definition, origin, usage, and examples.',
      inputSchema: zodToJsonSchema(redditExplainSchema) as any,
      readOnlyHint: true
    }
  • Dispatch handler in the tool call switch statement that invokes the redditExplain method with parsed arguments.
    case 'reddit_explain':
      result = await tools.redditExplain(
        redditExplainSchema.parse(args)
      );
      break;
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the return content ('definition, origin, usage, and examples'), which adds some context, but it does not cover important traits like error handling, rate limits, authentication needs, or data sources. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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 highly concise and front-loaded, consisting of two sentences that directly state the purpose and return values. Every sentence earns its place by providing essential information without redundancy or unnecessary details, making it efficient and easy to understand.

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

Completeness3/5

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

Given the tool's low complexity (one parameter, no output schema, no annotations), the description is minimally adequate. It covers the purpose and return content, but lacks details on behavioral aspects and usage context. Without annotations or output schema, it should do more to explain how the tool behaves and when to use it, but it meets the basic requirements for a simple lookup tool.

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?

The input schema has 100% description coverage, with the 'term' parameter clearly documented. The description does not add any additional meaning beyond the schema, such as examples of terms or usage nuances. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description does not compensate but also does not detract.

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

Purpose4/5

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

The description clearly states the tool's purpose: 'Get explanations of Reddit terms, slang, and culture.' It specifies the verb ('Get explanations') and resource ('Reddit terms, slang, and culture'), making the function unambiguous. However, it does not explicitly differentiate from sibling tools like 'user_analysis' or 'search_reddit', which might also involve Reddit terminology, so it lacks sibling differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention any context, exclusions, or prerequisites, such as when to prefer this over 'search_reddit' for term definitions or how it relates to other tools. Without such information, users must infer usage from the purpose alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/karanb192/reddit-mcp-buddy'

If you have feedback or need assistance with the MCP directory API, please join our Discord server