Skip to main content
Glama

dog_api_breeds

Read-onlyIdempotent

List dog breeds with details from The Dog API and paginate results using page and limit parameters for manageable browsing.

Instructions

List dog breeds with details from The Dog 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_api_breeds"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default 0)
limitNoNumber of breeds to return (max 50, default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered. The description adds nothing beyond source attribution — no note on pagination behavior, result ordering, total counts, or what 'details' includes, which is exactly the context an agent would need.

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 short sentence with the purpose front-loaded and no filler. It is efficient, though the brevity is partly what leaves the gaps elsewhere.

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

Completeness3/5

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

For a simple read-only list tool with complete schema docs and safety annotations, the description is minimally sufficient to call the tool. It still lacks the sibling disambiguation that the crowded dog/cat breed namespace makes necessary.

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 page and limit fully documented including defaults and the 50-item cap. The description adds no parameter meaning, so the baseline 3 for fully documented schemas applies.

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

Purpose3/5

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

States a verb and resource ('List dog breeds') and adds the data source, but the sibling set contains dog_list_breeds, dog_breed_list, and dog_breed_image, and the description gives no basis for choosing between them. An agent cannot distinguish this from those siblings without opening each schema.

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 mention of the closely named alternatives, and no stated conditions or prerequisites. The agent must infer usage entirely from the name.

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