Skip to main content
Glama

official_joke_ten

Read-onlyIdempotent

Fetch 10 random jokes from the Official Joke API for use in testing, demos, or content generation.

Instructions

Get 10 random jokes from Official Joke API.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, non-destructive, open-world and idempotent, so the safety profile is covered. The description adds the source API and the random-selection trait, but says nothing about what the jokes look like (types, structure) or whether repeated calls return the same set. Nothing here contradicts the annotations, since a random read with no side effects still fits readOnly/idempotent.

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?

A single short sentence with the action, count, and data source front-loaded, and no wasted clauses. Nothing is padded or repeated from 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-only utility with full annotation coverage and no output schema, the description supplies enough to call it correctly. The one meaningful gap is whether the ten jokes are mixed types or uniform, which matters given the existence of official_joke_by_type.

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 the schema needs no explanation and the baseline is 4. The description correctly implies no inputs are required and adds the fixed count of 10, which is the only behavioral detail a caller needs.

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 names a specific verb and resource plus a quantity: fetch 10 random jokes from the Official Joke API. It implicitly separates itself from official_joke_random (single joke) by stating the count, but it never names the sibling, so an agent must infer the distinction rather than read it.

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?

Usage is only implied: the fixed count of 10 signals this is the bulk variant versus official_joke_random or official_joke_by_type, which an agent can reason about. There is no explicit when-to-use, when-not-to-use, or alternative routing statement.

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

Deploy Server

Other Tools