Skip to main content
Glama

Rescuegroups Breeds

rescuegroups_breeds
Read-onlyIdempotent

Breeds RescueGroups recognises for a species, for building an exact breed filter. Requires your own RescueGroups API key. Example: rescuegroups_breeds({ species: "dogs", limit: 50, _apiKey: "your-key" })

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": {
      "limit": 50,
      "_apiKey": "your-rescuegroups-api-key",
      "species": "dogs"
    },
    "name": "rescuegroups_breeds"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage of results, starting at 1.
limitNoRows per page. This endpoint allows up to 10000. Default 250.
_apiKeyYesYour own RescueGroups API key. Request a free public API key at https://rescuegroups.org/services/request-an-api-key/ a short form (name, email, organisation, site URL). It is open to individual developers: "not incorporated" is an accepted answer and you do not need to be a rescue or shelter. RescueGroups staff review it and email the key back, so it is not instant. Then pass the key as the `_apiKey` argument.
speciesNoSpecies whose breeds to list, plural and lower-case, e.g. "dogs". Omit for every breed across all species (thousands of rows, page it).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"Your own RescueGroups API key. Request a free public API key at https://rescuegroups.org/services/request-an-api-key/ — a short form (name, email, organisation, site URL). It is open to individual developers: \"not incorporated\" is an accepted answer and you do not need to be a rescue or shelter. RescueGroups staff review it and email the key back, so it is not instant. Then pass the key as the `_apiKey` argument."New value: +"Your own RescueGroups API key. Request a free public API key at https://rescuegroups.org/services/request-an-api-key/ a short form (name, email, organisation, site URL). It is open to individual developers: \"not incorporated\" is an accepted answer and you do not need to be a rescue or shelter. RescueGroups staff review it and email the key back, so it is not instant. Then pass the key as the `_apiKey` argument."
    • changedInput schema / properties / species / description
      Previous value: -"Species whose breeds to list, plural and lower-case, e.g. \"dogs\". Omit for every breed across all species (thousands of rows — page it)."New value: +"Species whose breeds to list, plural and lower-case, e.g. \"dogs\". Omit for every breed across all species (thousands of rows, page it)."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare the operation as read-only, idempotent, open-world, and non-destructive. The description adds the important authentication requirement (your own API key) and an example, but does not describe pagination behavior, result size, or other runtime traits beyond what the schema covers.

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?

The description is short, front-loaded with the core purpose, and includes a compact example. Every sentence carries useful information, though the phrasing 'Breeds RescueGroups recognises' is slightly awkward.

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 list tool with no output schema, the description covers the essential purpose, API key requirement, and a usage example. The schema fills in pagination and species omission behavior, so the description is largely complete, though it could mention what happens when species is omitted.

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 all four parameters are already documented in detail, including the species enum and API key instructions. The description's example restates the parameter names without adding meaning 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?

The description clearly states the resource (breeds) and its scoping (for a species), and adds the use case of building an exact breed filter. It does not explicitly differentiate from siblings like rescuegroups_species, but the purpose is specific enough to distinguish it from animal or organization tools.

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?

It implies when to use it by saying 'for building an exact breed filter' and provides an example call. However, it gives no explicit when-not-to-use guidance or named alternatives, leaving the agent to infer that rescuegroups_species lists species rather than breeds.

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.