Skip to main content
Glama

Rescuegroups Species

rescuegroups_species
Read-onlyIdempotent

The species vocabulary RescueGroups uses, singular, plural and young-animal words for each species it lists. Use it to get the exact species value rescuegroups_adoptable expects. Requires your own RescueGroups API key. Example: rescuegroups_species({ _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": {
      "_apiKey": "your-rescuegroups-api-key"
    },
    "name": "rescuegroups_species"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage of results, starting at 1.
limitNoRows per page, 1-250. Default 250 (the whole list is small).
_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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the call requires the caller's own RescueGroups API key, and the payload is a small fixed vocabulary of species name forms. It doesn't mention caching or rate limits, which keeps it below 5.

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?

Three short sentences, front-loaded with what the tool returns and then why to call it, followed by a compact example. The API-key sentence is mildly redundant with the extensive _apiKey schema description, but it is one clause and does not bloat the definition.

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?

There is no output schema, so the description carries the burden of describing the return value, and it does so adequately by naming the singular/plural/young-animal word forms returned. Auth prerequisites and sibling linkage are covered; only minor details like result ordering or whether the list is cached are absent, which is acceptable for a small static vocabulary.

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 _apiKey, page and limit parameters are each documented in detail in the schema, so the baseline of 3 applies. The description only reiterates the API-key requirement and shows an example call; it adds no new semantics for paging or limits 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 first sentence names the specific resource (the species vocabulary, including singular, plural and young-animal forms) and the second states the concrete job it performs: supplying the exact `species` value that rescuegroups_adoptable expects. An agent can distinguish it from rescuegroups_breeds or rescuegroups_animal without opening any 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?

"Use it to get the exact `species` value rescuegroups_adoptable expects" gives explicit routing to the sibling that consumes its output, which is strong positive guidance. It stops short of stating when not to call it (e.g. if you already know the species string or only need breed lookup), so it is not a full 5.

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.