Skip to main content
Glama
Sign In

Dadjokes

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Random Joke

random_joke
Read-onlyIdempotent

Fetch one random dad joke from icanhazdadjoke.com. Returns joke text and alphanumeric ID.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "random_joke"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
idYesUnique identifier for the joke
jokeYesThe joke text

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
    • 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"
+}
  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 declare readOnlyHint, idempotentHint, and destructiveHint, so safety profile is covered. The description adds valuable context by naming the external source (icanhazdadjoke.com) and the exact return shape (joke text and ID), which goes beyond annotations.

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 short sentences with no filler. The key verb and resource are front-loaded, and every word adds meaning.

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?

The tool is simple, has an output schema, and annotations cover safety. The description provides enough behavioral context (source, return values) to be fully understood without any gaps.

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?

There are zero parameters and the schema coverage is 100%, so the baseline is 4. The description adds no parameter-specific details, but none are needed since the tool takes no input.

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 starts with the specific verb 'Fetch' and clearly identifies the resource: 'one random dad joke from icanhazdadjoke.com'. It also states the return values ('joke text and alphanumeric ID'), which distinguishes it from sibling tools like get_joke (specific joke) and search_jokes (search).

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 context: use this when you need a random dad joke. It does not explicitly name alternatives or exclusions, but the 'random' qualifier clearly separates it from search/get siblings, providing clear context without needing explicit contrast.

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

All Dadjokes toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources