Skip to main content
Glama

Dogceo

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Breed Images

breed_images
Read-onlyIdempotent

Get multiple dog photos for a specific breed (e.g., 'labrador', 'poodle'). Returns array of image URLs. Use when you need a gallery of one breed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
breedYesThe breed name (e.g. "hound", "labrador"). Use list_breeds to see valid values.
countNoNumber of images to return. Defaults to 3.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hintNoHint message if breed not found
breedYesThe requested breed name
foundYesWhether the breed was found
image_urlsYesArray of image URLs for the breed

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "breed": {
+      "description": "The requested breed name",
+      "type": "string"
+    },
+    "found": {
+      "description": "Whether the breed was found",
+      "type": "boolean"
+    },
+    "hint": {
+      "description": "Hint message if breed not found",
+      "type": "string"
+    },
+    "image_urls": {
+      "description": "Array of image URLs for the breed",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "breed",
+    "found",
+    "image_urls"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "breed": "labrador"
+  },
+  {
+    "breed": "golden_retriever",
+    "count": 5
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The description discloses the return format ('array of image URLs'), adding value beyond the annotations' read-only and idempotent hints. It also gives examples of valid inputs, though it doesn't cover edge cases like unknown breeds or count behavior, which are handled by the schema.

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?

The description is two sentences, front-loaded with the core action and resulting format, with zero filler. It's a model of brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity, the 100% schema coverage of parameters, and the presence of an output schema, the description covers the essential purpose and use case. The only minor omission is explicit mention of default count, but that's in the schema.

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 parameters are fully documented in the schema. The description adds example values ('labrador', 'poodle') and implicitly references valid breed names, but adds no additional parameter semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the specific verb 'Get' with a clear resource ('multiple dog photos') and scope ('for a specific breed'), supported by concrete examples. This clearly differentiates from sibling tools like random_breed_image (single random) and list_breeds (which enumerates breeds).

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?

The phrase 'Use when you need a gallery of one breed' provides a clear use-case scenario. It implies distinction from random image tools, though it doesn't explicitly name alternatives or exclusions.

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

All Dogceo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources