Skip to main content
Glama

Dogsapi List Breeds

dogsapi_list_breeds
Read-onlyIdempotent

Search dog breeds with pagination. Returns breed names, IDs, weight ranges, life spans, and hypoallergenic status. Use get_breed for detailed info on a specific breed.

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": {
      "page": 1
    },
    "name": "dogsapi_list_breeds"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for pagination (default: 1)

Output Schema

NameRequiredDescriptionDefault
pageYesPage number requested
totalYesTotal count of breeds available
breedsYesArray of dog breeds on this page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world semantics, so the safety profile is covered. The description adds the useful fact that results are paginated and enumerates what the response contains (names, IDs, weight ranges, life spans, hypoallergenic status). It does not state page size or total-count behavior, which would be the remaining piece of pagination context.

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: purpose first, then return contents, then the sibling hand-off. Nothing is wasted and the most decision-relevant information is front-loaded.

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 read-only, single-optional-parameter list tool with a full input schema and an output schema, this covers purpose, contents, and the sibling alternative. Slight over-disclosure of return fields (already implied by the output schema) and the missing page-size detail keep it just short of complete.

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 a single optional page parameter already documented with its default in the schema. The description only echoes "pagination" without adding format, page-size, or out-of-range behavior, so baseline 3 applies.

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?

States a specific verb and resource ("Search dog breeds") plus scope ("with pagination"), and explicitly contrasts itself with the sibling get_breed for detail lookup. An agent can distinguish this list tool from the detail tool without opening either schema.

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?

Gives an explicit routing rule: use get_breed when you need detailed info on one breed, implying this tool is for browsing/listing. It stops short of stating when *not* to use it (e.g., no filtering/search-by-name) or other exclusions, so it is clear context but not a full when/when-not rule set.

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.