Skip to main content
Glama

dog_breed_list

Read-onlyIdempotent

Lists sub-breeds for a specified dog breed so users can explore related breed variations from a given breed name.

Instructions

List sub-breeds of a specific dog breed.

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": {
      "breed": "<breed>"
    },
    "name": "dog_breed_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
breedYesBreed name (e.g. bulldog, hound)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior, so safety is covered. The description adds only that the result is a list scoped to sub-breeds, without explaining return format, whether breed matching is exact or partial, or error behavior for unknown breeds. With annotations present, this is adequate but thin.

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 a single front-loaded sentence with no filler. Every word contributes to stating the action and resource. Nothing is buried or repeated.

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 simple read-only lookup with full schema coverage and clear annotations, the description is nearly sufficient. It states the scoped list operation, though it could note that the result is a list of sub-breed names to fully set expectations. Overall it is complete enough for correct tool selection and invocation.

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%, and the breed parameter already documents that it expects a breed name with examples like bulldog and hound. The description reinforces the single-breed scope but adds no syntax, matching rules, or format details beyond the schema. Baseline 3 is appropriate when the schema carries parameter semantics.

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?

The description uses a specific verb and resource: "List sub-breeds of a specific dog breed." It is clearly distinct from sibling tools like dog_list_breeds or dog_api_breeds that list all breeds, though it does not explicitly name those alternatives. The scope is understandable without opening the schema.

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 phrase "of a specific dog breed" implies the tool is used when a breed name is already known, but it does not explicitly say when to choose this over dog_list_breeds or dog_api_breeds. There are no exclusions or prerequisites stated. Usage is inferable but not fully guided.

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