Skip to main content
Glama

AutoTasker Hub — China Social Data API

random_dog_image

Random dog image URL by breed via Dog CEO. $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_dog_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
breedNoOptional breed, e.g. husky

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does add real behavioral context the schema lacks: the price ($0.01 USDC) and the upstream provider (Dog CEO), which tells an agent this is a metered external call. It does not disclose what happens with an invalid breed (error vs. fallback), rate limits, or whether the returned URL is a direct image file.

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 terse clauses, each earning its place: what is returned, and what it costs. Front-loaded with the resource and output type, with no filler or restated name.

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 one-optional-parameter read tool with no output schema, the essentials are present: the return value shape (URL), the provider, the price, and the optional breed filter. The only meaningful gap is undefined behavior for an unrecognized breed.

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 single parameter is fully documented in the schema, including an example value, so baseline is 3. The description's "by breed" confirms the filtering intent but adds no format, casing, or validity detail beyond the schema's "e.g. husky".

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?

"Random dog image URL by breed" names a specific resource (dog image) and output (URL), and the provider (Dog CEO) anchors it. It distinguishes itself from siblings like random_cat_image and random_bear_image by the resource noun, though it never explicitly contrasts with random_dog_placeholder or dog_breed_list.

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 implied by the purpose: call it to get a random dog picture, optionally constrained by breed. There is no explicit when-not guidance and no mention of siblings such as dog_breed_list for discovering valid breed values or random_dog_placeholder as the non-random alternative. The cost note hints that this is a paid call, but no routing guidance is given.

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.