Skip to main content
Glama

Rescuegroups Organizations

rescuegroups_organizations
Read-onlyIdempotent

Find animal rescues and shelters with RescueGroups.org accounts: name, type (Rescue or Shelter), address, phone, email, website, adoption process, areas served and services. Filter by postal-code radius, state or name. Requires your own RescueGroups API key. Example: rescuegroups_organizations({ postalcode: "15206", miles: 25, limit: 5, _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": 5,
      "miles": 25,
      "_apiKey": "your-rescuegroups-api-key",
      "postalcode": "15206"
    },
    "name": "rescuegroups_organizations"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoLatitude to search around. Use with `lon`.
lonNoLongitude to search around. Use with `lat`.
cityNoCity name.
nameNoMatch the organization name (substring).
pageNoPage of results, starting at 1.
sortNoField to sort by, "-" prefixed for descending, e.g. "orgs.name". On a distance search "distance" sorts nearest-first.
typeNoRestrict to rescues or to shelters. Omit for both.
limitNoRows per page, 1-250. Default 25.
milesNoRadius in miles. Provide exactly one of `miles` or `kilometers`.
stateNoTwo-letter state or province code, e.g. "PA".
org_idNoFetch one organization by id instead of searching.
_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.
kilometersNoRadius in kilometres. Provide exactly one of `miles` or `kilometers`.
postalcodeNoUS or Canadian postal/zip code to search around. Requires `miles` or `kilometers`.

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 cover readOnly, idempotent, open-world and non-destructive behavior, so the bar is lower. The description still adds value by disclosing the external auth requirement (your own RescueGroups API key) and by listing the returned fields, though it says nothing about pagination or rate limits.

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 purpose sentence front-loads the resource and the returned fields, followed by the filter options, the API-key requirement and a compact example. There is no filler, though the API-key sentence is somewhat redundant with the schema's own description.

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?

With 14 parameters and no output schema, the description compensates by naming the fields returned, which the structured data does not cover. It is missing guidance on pagination and on the exclusive miles/kilometers choice, but nothing critical to invoking the tool correctly is absent.

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 the schema already documents all 14 parameters with units, defaults and enum values. The description's mention of filtering by radius, state or name restates what the schema provides rather than adding syntax or constraints, so it meets but does not exceed the baseline.

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 ('Find animal rescues and shelters') and enumerates the returned fields, which cleanly separates it from the animal/adoptable siblings by domain. An agent can tell what this tool returns without opening the 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?

It states the supported filter modes (postal-code radius, state, name) and gives a worked example call, which conveys a clear use context. It does not explicitly exclude sibling tools or say when to prefer them, so it falls short of a 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.