Skip to main content
Glama

honestdog

by de.honestdog
OverviewDiscussionsAdmin

Search adoptable shelter dogs

search_shelter_dogs
Read-onlyIdempotent

Use when someone wants to adopt a dog from a shelter in Germany, e.g. 'adopt a dog in Berlin' or 'Hund aus dem Tierheim adoptieren Bayern'. Searches dogs currently listed for adoption by German partner shelters on HonestDog (coverage is still small — a few shelters, mostly mixed breeds), by breed (German or English), size, gender, or Bundesland. Returns name, photos (only where the shelter consented), age in years, size, shelter and the honestdog.de listing URL; adoption happens with the shelter via the linked pages. / Durchsucht die aktuell zur Adoption gelisteten Tierheimhunde nach Rasse, Größe, Geschlecht oder Bundesland.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeNoSize class (shelters list sizes in German; mapped server-side)
limitNo
stateNoGerman Bundesland of the shelter, e.g. 'Nordrhein-Westfalen' (English names like 'North Rhine-Westphalia' are mapped)
genderNo
breed_textNoBreed in German or English, umlauts optional (e.g. 'Schäferhund', 'german shepherd', 'Mischling'); matched against the shelter's breed text and HonestDog's breed catalogue

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / breed_text / description
      Previous value: -"Breed text as listed by the shelter (substring match)"New value: +"Breed in German or English, umlauts optional (e.g. 'Schäferhund', 'german shepherd', 'Mischling'); matched against the shelter's breed text and HonestDog's breed catalogue"
    • addedInput schema / properties / size / description
      Added value: +"Size class (shelters list sizes in German; mapped server-side)"
    • addedInput schema / properties / size / enum
      Added value: +[
+  "small",
+  "medium",
+  "large",
+  "giant"
+]
    • removedInput schema / properties / size / maxLength
      Removed value: -30
    • changedInput schema / properties / state / description
      Previous value: -"German Bundesland of the shelter"New value: +"German Bundesland of the shelter, e.g. 'Nordrhein-Westfalen' (English names like 'North Rhine-Westphalia' are mapped)"
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower — and the description still adds real context: small coverage ('a few shelters, mostly mixed breeds'), photos only where the shelter consented, and that adoption completes off-platform via the linked listing pages.

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 the trigger condition and efficient; every sentence carries information. The full German translation roughly doubles the length and is redundant for an agent, though it is a deliberate bilingual choice for a German-market tool.

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?

With no output schema, the description carries the return contract itself — name, consented photos, age in years, size, shelter, and the honestdog.de listing URL — plus the coverage limitation. Nothing an agent needs to call or interpret this correctly is missing.

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 60% and the schema already documents the notable semantics (size mapped from German, state English-name mapping, bilingual breed matching). The description merely recaps the filter dimensions ('breed (German or English), size, gender, or Bundesland') without adding new meaning, and never explains the limit parameter.

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 ('Searches dogs currently listed for adoption by German partner shelters on HonestDog') plus the filter dimensions. The resource (shelter dogs for adoption) is distinct from the sibling search_breeders, so an agent can separate them without opening either 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 when someone wants to adopt a dog from a shelter in Germany' with two concrete example utterances gives clear trigger conditions. It does not explicitly name an alternative or a when-not case (e.g. use search_breeders for buying from breeders), so it stops 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.

All honestdog 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