Skip to main content
Glama

dog_random_image

Read-onlyIdempotent

Fetch one or more random dog images from the Dog CEO API by specifying an image count from 1 to 50.

Instructions

Get random dog image(s) from Dog CEO 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": "dog_random_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoNumber of images (1-50, default 1)

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 readOnly, idempotent, open-world, and non-destructive behavior, so the safety profile is covered. The description adds only the source API and the fact that multiple images can be returned; it says nothing about rate limits, response shape, or failure modes beyond what annotations imply.

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 front-loaded sentence with no filler. It is appropriately sized for a simple tool, though it is so short that it omits useful routing context rather than being wasteful.

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?

The tool is simple, the single parameter is fully documented, and annotations cover the safety and openness profile, so little more is required. The missing piece is sibling differentiation, which matters given the crowded image-endpoint namespace.

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%, so the 'count' parameter (1-50, default 1) is fully documented in the schema itself. The description's '(s)' hints at the batch capability but adds no formatting or behavior detail beyond the schema, so baseline 3 applies.

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 random dog image(s)') and names the source ('Dog CEO API'), so the agent knows exactly what it returns. It does not differentiate from near-duplicate siblings such as dog_api_random_image or dog_breed_image, though the API source does separate it from generic image tools.

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 guidance, no exclusions, and no mention of alternatives like dog_breed_image (breed-specific) or dog_api_random_image. With many dog/cat/image siblings in the list, the agent must infer selection from the name alone.

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