Skip to main content
Glama

chucknorris

by io.github.pipeworx-io

Random Joke

random_joke
Read-onlyIdempotent

Fetch one random Chuck Norris joke from chucknorris.io. Returns joke text, unique ID, category list, and permalink URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesUnique joke identifier
urlYesURL to the joke on chucknorris.io
jokeYesThe joke text
categoriesYesList of categories

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "categories": {
+      "description": "List of categories",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "id": {
+      "description": "Unique joke identifier",
+      "type": "string"
+    },
+    "joke": {
+      "description": "The joke text",
+      "type": "string"
+    },
+    "url": {
+      "description": "URL to the joke on chucknorris.io",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "joke",
+    "categories",
+    "url"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {}
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "id": {
-      "description": "Unique identifier for the joke",
-      "type": "string"
-    },
-    "joke": {
-      "description": "The joke text",
-      "type": "string"
-    }
-  },
-  "required": [
-    "id",
-    "joke"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "id": {
+      "description": "Unique identifier for the joke",
+      "type": "string"
+    },
+    "joke": {
+      "description": "The joke text",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "joke"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
  5. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only and idempotent behavior. The description adds useful context by naming the external API (chucknorris.io), implying potential network dependency, and listing the exact return fields, which goes beyond the safe-read annotation.

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, front-loaded with the action, and every sentence adds value. It states the source, the action, and the return payload without superfluous words.

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

Completeness5/5

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

For a zero-parameter tool with an output schema, the description adequately covers the purpose and return values. It mentions all key output fields (joke text, ID, category list, permalink) and gives the external source, making the tool behaviorally complete for an 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 tool has zero parameters, so the description does not need to explain parameter behavior. The baseline for zero-parameter tools is 4, and the description does not introduce any irrelevant parameter details.

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 a specific action ('Fetch one random Chuck Norris joke') and identifies the external source (chucknorris.io). This distinguishes it from sibling tools like joke_by_category and search_jokes, which have different purposes.

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

Usage Guidelines4/5

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

The description implies usage for obtaining a random joke, and the sibling list gives context for alternatives, but it does not explicitly state when to use this tool over others or mention exclusions. Still, the context is clear enough for a user to infer the appropriate use case.

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

All chucknorris toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation2/5

Several tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical query routers, and the five polymarket_* tools all hunt mispricings in subtly different ways. The memory trio (remember/recall/forget) and subscription trio (subscribe/unsubscribe/recent_alerts) are distinct, but the many data-query tools create frequent ambiguity for an agent deciding which one to call.

Naming Consistency2/5

Naming is a mix of verb_noun (list_categories, resolve_entity, validate_claim), bare nouns (entity_profile, random_joke, deep_research), single verbs (forget, recall), and brand-prefixed nouns (pipeworx_feedback, pipeworx_trending). There's no consistent pattern across the set, so an agent cannot predict a tool's name from its function.

Tool Count1/5

35 tools for a server named 'chucknorris' is an extreme mismatch; only 4 tools actually relate to Chuck Norris jokes. The rest form a sprawling collection of data-research, prediction-market, subscription, and memory utilities that have nothing to do with the stated server identity and overwhelm any agent expecting a simple joke API.

Completeness2/5

The Chuck Norris joke subset is complete (random, by-category, search, categories), but the overall server attempts many unrelated domains—structured data queries, prediction-market arb, entity profiles, subscriptions, memory—none of which are clearly scoped or fully coherent. The result is a grab-bag with no single domain that feels finished, and the incongruous inclusion of joke tools adds confusion rather than coverage.

Resources