Skip to main content
Glama

Rescuegroups Animal

rescuegroups_animal
Read-onlyIdempotent

Full record for one adoptable animal by RescueGroups id, description, all photos, breeds, adoption fee, temperament and the listing rescue/shelter with its contact details. Requires your own RescueGroups API key. Example: rescuegroups_animal({ animal_id: "8013243", _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",
      "animal_id": "8013243"
    },
    "name": "rescuegroups_animal"
  }
}

Input Schema

NameRequiredDescriptionDefault
_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.
animal_idYesRescueGroups animal id, as returned in the `id` field by rescuegroups_adoptable.

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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false. The description adds useful context beyond them: the tool returns a full record including photos and shelter contact details, and requires the caller to supply their own API key. It omits rate-limit or error behavior, keeping it just short of a 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?

The definition is front-loaded with the core purpose, then the returned fields, then the prerequisite, then an example. It is tight overall, though the example partly duplicates the schema's examples block, which is minor redundancy.

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

Completeness5/5

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

For a simple two-parameter read tool with no output schema, the description is complete: it explains the returned payload, the authentication requirement, and the id source. Annotations cover safety, so nothing essential is missing before calling it.

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%, so both parameters are already documented in the input schema, including how to obtain the _apiKey and where animal_id comes from. The description adds the example call but no new semantic detail about parameter formats, so the 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?

The description opens with a specific verb and resource: 'Full record for one adoptable animal by RescueGroups id,' and enumerates what the record contains (photos, breeds, fee, temperament, shelter contact). This clearly distinguishes it from the list-style sibling rescuegroups_adoptable.

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?

It states the required input (a RescueGroups id), notes the prerequisite of a personal API key, and includes a concrete call example. It does not explicitly say 'use rescuegroups_adoptable to find ids first,' though the schema's animal_id description does that routing, so context is clear but not fully self-contained.

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.