Skip to main content
Glama
Sign In

Dadjokes

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Dadjokes Random Joke

dadjokes_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": "dadjokes_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. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare read-only, open-world, idempotent, and non-destructive behavior, so the safety profile is covered. The description adds the external dependency (icanhazdadjoke.com), which is meaningful context for an open-world call. It does not mention rate limits, availability behavior, or what happens if the upstream service fails.

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?

Two short sentences, front-loaded with the action and resource, followed by the return shape. No filler or repetition of the title.

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

Completeness4/5

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

For a zero-parameter read tool with annotations and an output schema, the description covers purpose, source, and return contents. It leaves out only upstream reliability/rate-limit context, which is minor here since the output schema handles return values.

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 takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly does not invent parameter guidance.

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 states a specific verb and resource ("Fetch one random dad joke") and names the upstream source (icanhazdadjoke.com). It does not explicitly contrast with the sibling dadjokes_get_joke, so the agent must infer the difference between "random" and a plain get.

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

Usage Guidelines3/5

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

The word "random" implies usage when no filtering or selection criteria are needed, which implicitly contrasts with dadjokes_search_jokes. However, there is no explicit when-to-use or when-not-to-use guidance against the close sibling dadjokes_get_joke.

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