Skip to main content
Glama
Sign In

Rescuegroups

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Rescuegroups Adoptable

rescuegroups_adoptable
Read-onlyIdempotent

Search adoptable animals listed by rescues and shelters on RescueGroups.org: name, breed, age, sex, size, temperament flags (good with kids/dogs/cats), photos, and the listing organization. Filter by species, postal-code radius, breed, sex, age group and size. Requires your own RescueGroups API key. Example: rescuegroups_adoptable({ species: "dogs", postalcode: "15206", miles: 50, limit: 5, _apiKey: "your-key" })

Input Schema

NameRequiredDescriptionDefault
latNoLatitude to search around. Use with `lon` and `miles`/`kilometers`. More precise than `postalcode`.
lonNoLongitude to search around. Use with `lat`.
sexNoRestrict to one sex.
nameNoMatch the animal's name (substring, e.g. "Curly").
pageNoPage of results, starting at 1. Use with `limit`; the response `pagination` block tells you how many pages there are.
sortNoField to sort by, prefixed with "-" for descending, e.g. "-animals.updatedDate" (most recently updated first) or "animals.name". On a distance search "distance" sorts nearest-first. Fully-qualified names like "animals.name" are what the API expects.
breedNoBreed to match, e.g. "Beagle". Matched as a substring against the animal's breed string, so "Retriever" matches "Golden Retriever". Call rescuegroups_breeds for exact names.
limitNoRows per page, 1-250. Default 25.
milesNoRadius in miles for a distance search. Provide exactly one of `miles` or `kilometers`; the returned `distance` field is in the same unit.
viewsNoExtra RescueGroups "views" to stack onto the search: "haspic" (has at least one photo), "isspecialneeds", "isneedingfoster", "urgent", "iscourtesylisting", "attending" (attending an adoption event).
org_idNoRestrict the search to one organization id (see rescuegroups_organizations).
_apiKeyYesYour own RescueGroups API key. Pipeworx has no shared key for this pack. 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 to search, spelled plural and lower-case as RescueGroups does (e.g. "dogs", "cats", "rabbits", "horses"). Omit to search every species at once. Call rescuegroups_species for the live list.
age_groupNoGeneral age band as RescueGroups classifies it.
kilometersNoRadius in kilometres for a distance search. Provide exactly one of `miles` or `kilometers`.
postalcodeNoUS or Canadian postal/zip code to search around, e.g. "15206". Requires `miles` or `kilometers`. RescueGroups uses the centre of the postal code, so this is less precise than lat/lon.
size_groupNoExpected adult size band.
good_with_catsNoOnly animals flagged OK with cats.
good_with_dogsNoOnly animals flagged OK with other dogs.
good_with_kidsNoOnly animals flagged good with children.
include_adoptedNoSearch already-adopted animals instead of available ones. Default false (only animals available for adoption).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/open-world, so the description's main added value is the authentication constraint: it warns there is no shared key and that users must request their own, which the agent must surface before calling. It does not add rate-limit or result-volume behavior beyond that.

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?

Front-loaded with purpose, then filters, then the auth prerequisite, then a concrete example — no filler sentences. The filter list is somewhat redundant with the schema, keeping it just under top marks.

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 21-parameter search tool with no output schema, the definition covers purpose, filter scope, the API-key prerequisite, and a working call shape. Return structure and pagination are left entirely to schema fields, which is acceptable given their 100% coverage.

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 enums and per-parameter notes, so the description's restatement of filter names adds little. The embedded example does show a realistic call combination (species + postalcode + miles + limit), which is useful but marginal against a fully documented 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?

States a specific verb and resource ("Search adoptable animals listed by rescues and shelters on RescueGroups.org") and enumerates the returned fields, so the agent knows exactly what a call yields. Its listing/search role is clearly distinct from the single-record sibling rescuegroups_animal, even though the sibling is not named.

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?

Gives filterable dimensions (species, postal radius, breed, sex, age group, size) which implies when the tool applies, but never states when NOT to use it or points to alternatives such as rescuegroups_animal for details or rescuegroups_breeds for exact breed names (the latter appears only in the schema).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Rescuegroups toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources