Skip to main content
Glama

cataas_random_cat

Read-onlyIdempotent

Fetch a random cat image for apps or workflows, with optional tag filtering and text overlay.

Instructions

Get a random cat image, optionally with a tag or text overlay.

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": "cataas_random_cat"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoFilter by tag (e.g. cute, funny, sleeping)
textNoText to overlay on the image

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that results are random and can be customized, but it says nothing about the return value (image URL vs. binary), rate limits, or the odd tension between idempotentHint=true and a tool that returns a different image on each call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single well-formed sentence with the core action front-loaded and optional modifiers trailing. Nothing is padded, though it is arguably too terse given the number of sibling tools an agent must choose between.

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

Completeness3/5

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

For a zero-required-param, no-output-schema tool, the description covers the call mechanics adequately, but with no output schema the return shape (image URL, redirect, base64) is undocumented, and the sibling ambiguity is unresolved. It is minimally sufficient rather than complete.

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?

Schema description coverage is 100%, with both `tag` and `text` documented including an example of tag values, so the schema does the heavy lifting. The description only restates that both are optional overlays/filters, adding no format, validation, or constraint details beyond the schema.

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?

States a specific verb and resource ("Get a random cat image") plus the two optional modifiers, so the action is unambiguous. However, it gives no signal distinguishing it from nearby siblings like cat_api_random_image, http_cat_image, or placekitten_image, all of which appear to fetch cat pictures.

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

Usage Guidelines2/5

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

There is no when-to-use / when-not-to-use guidance and no comparison against alternatives, despite several overlapping cat-image siblings in the tool set. The phrase "optionally with a tag or text overlay" hints at capability but not at routing decisions.

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