Skip to main content
Glama

http_dog_image

Read-onlyIdempotent

Retrieve a dog image URL mapped to any HTTP status code (100–599) to visualize HTTP responses like httpcat but with dogs.

Instructions

Get a dog image URL for an HTTP status code (like httpcat but with dogs).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "status_code": "<status_code>"
    },
    "name": "http_dog_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
status_codeYesHTTP status code (100-599).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description still adds real value by disclosing that the return is a URL rather than image bytes and that output is a fixed per-code mapping (httpcat-style), which no output schema supplies.

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?

One sentence, front-loaded with the action and resource, with the analogy doing compact explanatory work. Nothing extraneous.

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 single-parameter, read-only lookup with rich annotations and no output schema, the description covers action, input semantics and return type (a URL). The only shortfall is the lack of sibling disambiguation against http_cat_image.

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 coverage is 100% with the 100-599 range documented on status_code, so the schema carries parameter meaning. The description reinforces that the code drives selection but adds no format or edge-case detail 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 (get) and resource (dog image URL) tied to an HTTP status code input, and the httpcat analogy pins down the mapping concept immediately. It does not distinguish itself from the sibling http_cat_image, which the agent must infer from the word 'dogs'.

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?

The httpcat comparison implies when this is useful (illustrating a status code), but there is no explicit when-to-use/when-not guidance, and the near-identical sibling http_cat_image is never named or ruled out.

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