Skip to main content
Glama
deenesjakoruzh
Hamzaaamin

Get Joke

by Hamzaaamin
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript

Get Joke MCP Server

Minimal Model Context Protocol (MCP) server (Node.js) that exposes one tool: get_joke.

Setup

npm install

Related MCP server: Jokes MCP Server

Run

node index.js

Or:

npm start

Test (without Inspector)

This repo includes a tiny SDK-based client that spawns the server over stdio, lists tools, and calls get_joke:

npm run test:mcp

Tool response shape

The get_joke tool returns JSON like:

{
  "joke": "Why do programmers prefer dark mode? Because light attracts bugs."
}

Publish to the MCP Registry (official)

The official MCP Registry stores metadata only, so you must publish the package to npm first.

  1. Publish to npm (once):

npm adduser
npm publish --access public

  1. Publish metadata to the MCP Registry:

brew install mcp-publisher
mcp-publisher login github
mcp-publisher publish

Notes:

  • package.json includes mcpName and server.json uses the same name (required for verification).

  • If you change the version, bump it in both package.json and server.json (and republish to npm).

Available Tools

1 tool
get_jokeB

Return a random programming joke as JSON.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the output format ('as JSON') but lacks details on randomness behavior, potential errors, rate limits, or other operational traits. This leaves the agent with incomplete information about how the tool behaves.

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 a single, efficient sentence that directly states the tool's function without any wasted words. It is appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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 simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate but lacks depth. It explains the output format but doesn't cover behavioral aspects like error handling or performance, leaving gaps in context for the agent.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately does not discuss parameters, earning a baseline score of 4 for not adding unnecessary information beyond what the schema already provides.

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 action ('Return') and resource ('a random programming joke as JSON'), making the purpose specific and understandable. However, with no sibling tools mentioned, there's no opportunity to distinguish from alternatives, so it cannot achieve a perfect score of 5.

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, prerequisites, or contextual constraints. It simply states what the tool does without any usage context, which is a significant gap in guidance.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev0.1.1
    • First observedget_joke
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.4/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'get_joke' has a clear and distinct purpose, making it impossible for an agent to misselect among non-existent alternatives.

Naming Consistency5/5

The single tool name 'get_joke' follows a consistent verb_noun pattern (get + joke). Since there is only one tool, there is no inconsistency in naming conventions to evaluate, and it adheres to a predictable style.

Tool Count2/5

A single tool is too few for most server purposes, as it limits functionality and scope. While it might suffice for a minimal joke service, it feels thin and lacks depth, potentially hindering more complex agent interactions or broader use cases.

Completeness3/5

Inferring the domain as joke retrieval, the tool 'get_joke' provides a basic operation. However, there are notable gaps: no ability to filter jokes by category, search for specific jokes, or manage a joke collection (e.g., create, update, delete), which limits the surface's utility for varied agent needs.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • Jokes MCP Server

    MinjoonHK
    -
    license
    Not graded
    quality
    Not graded
    maintenance
    Enables users to retrieve various types of jokes including Chuck Norris and Dad jokes through natural language requests. Demonstrates MCP integration with Microsoft Copilot Studio and GitHub Copilot for humor-focused AI interactions.
    -

  • Joke MCP Server

    ericqian77
    -
    license
    Not graded
    quality
    Not graded
    maintenance
    Enables developers to retrieve short jokes in multiple categories and languages during task processing. Provides fast offline fallbacks and configurable joke providers for entertainment during development workflows.
    -

  • Jokes MCP Server

    stefan-tuertscher
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables users to fetch jokes from various categories including Chuck Norris jokes and dad jokes. Provides a humor-focused experience through natural language requests integrated with Microsoft Copilot Studio.
    MIT

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/Hamzaaamin/Get-Joke'

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