Skip to main content
Glama

AutoTasker Hub — China Social Data API

random_cat_image

Random cat image URL via TheCatAPI public endpoint. $0.01 USDC.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose two genuinely useful traits: the upstream is a public endpoint (no auth) and each call costs $0.01 USDC (payside effect). It does not say whether the URL is ephemeral, what the rate limits are, or whether the returned image is fixed-size, so the safety/cost profile is only partly covered.

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?

Two short sentences, zero filler, with the payload description front-loaded before the cost caveat. It errs slightly toward under-specification rather than bloat, but no sentence is wasted.

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, single-value tool with no output schema, the description covers the essentials: what is returned (an image URL), where it comes from, and what it costs. Only edge details such as URL lifetime or response wrapper would add meaningfully more.

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 nothing for the description to disambiguate and the baseline of 4 applies. No misleading parameter language is present.

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 the specific resource (a random cat image URL) and the upstream source (TheCatAPI public endpoint), which distinguishes it from the dog/bear/fox siblings by resource alone. It is a noun phrase rather than an explicit verb+object, but there is no ambiguity about what calling it yields.

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?

No when-to-use, when-not-to-use, or alternative routing is stated; the only implicit guidance is the resource name itself. The '$0.01 USDC' note is a useful cost signal an agent could weigh against free siblings, but it is presented as a price tag, not as guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.