Skip to main content
Glama

Dog CEO (Unofficial)

Dogceo Random Image

dogceo_random_image
Read-onlyIdempotent

Get a random dog photo. Returns image URL and breed name. Use when you need any dog picture without a specific breed preference.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
image_urlYesURL of a random dog image

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds the return shape, but the tool has an output schema that already documents that, so little new behavioral context is contributed. It also does not address whether repeated calls yield different photos, which is the one behavior an agent might actually wonder about here.

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?

Three short sentences with the action first, then the return value, then the selection condition. Every sentence carries distinct information and nothing is repeated from the name or annotations.

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 tool with full annotation coverage and an output schema, the description covers purpose, returns and usage context. The only minor gap is that it does not mention variability between calls or any failure mode, though neither is essential for a trivial random-image fetch.

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 baseline is 4 and there is nothing for the description to clarify or omit. 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?

"Get a random dog photo" gives a specific verb and resource, and the follow-up sentence names the returned fields (image URL and breed name). The phrase "without a specific breed preference" implicitly separates it from a breed-scoped sibling, but the sibling is never named explicitly.

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

Usage Guidelines4/5

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

"Use when you need any dog picture without a specific breed preference" states a clear selection condition and implicitly rules out the breed-specific case. It stops short of naming the alternative tool, so the agent must infer which sibling handles breed requests.

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.