Skip to main content
Glama
Sign In

Dadjokes

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Joke

get_joke
Read-onlyIdempotent

Retrieve a specific dad joke by ID. Returns the full joke text.

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": {
      "id": "R7UfaahbfFd"
    },
    "name": "get_joke"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe ID of the dad joke to retrieve.

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: +[
+  {
+    "id": "R7UfaahbfFd"
+  }
+]
    • 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: -[
-  {
-    "id": "R7UfaahbfFd"
-  }
-]
    • 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: +[
+  {
+    "id": "R7UfaahbfFd"
+  }
+]
  5. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the core safety profile. The description adds that it 'Returns the full joke text,' which is useful but does not disclose error behavior, rate limits, or other potential edge cases. This is consistent with the reduced burden when annotations are present.

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 sentence, concise, and front-loaded with the verb and resource. Every word conveys essential information without redundancy, making it highly efficient.

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 simple lookup tool with one parameter, full schema coverage, and comprehensive annotations (readOnly, idempotent, non-destructive), the description is complete. The existence of an output schema further reduces the need to explain return values. The tool's behavior is fully captured by the current description.

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 provides 100% coverage with a clear description for the single 'id' parameter ('The ID of the dad joke to retrieve'). The tool description does not add additional parameter semantics beyond what the schema already documents, so the baseline of 3 is appropriate.

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 uses the specific verb 'Retrieve' and clearly identifies the resource as 'a specific dad joke by ID.' It distinguishes itself from siblings like random_joke and search_jokes by focusing on retrieval by ID, making its purpose immediately clear.

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 the appropriate use case: when you have a specific joke ID and want the full joke text. It does not explicitly name alternatives or provide exclusions, but the context ('by ID') gives clear guidance. Without explicit comparison to random_joke or search_jokes, it falls just short of a 5.

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