Petnecto

Show pets to adopt

show_pets

Read-onlyIdempotent

Show adoptable pets near a place as an interactive view: photos, facts, and a button to meet one at its rescue. Use it when someone wants to look at pets to adopt. Apps without interactive views get the same list as text.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Words in the person's own language: breeds, colors, ages, sizes, sex and places become filters ("black shiba girl Taipei", "黑色柴犬", "perro mayor"); other words are full-text search
`km`	No	Radius in kilometres, instead of miles
`age`	No
`sex`	No
`lang`	No	The person's language for names and text: en, es, zh-Hant, zh-Hans, ko, ja, vi, fr, ar, tl (default en)
`near`	No	Where the person is: a US ZIP (65738), lat,lon (25.03,121.56; rounded to ~1 km), or a Taiwan county or township in any language (信義區, Xinyi, 臺北市). Results are sorted by distance. Prefer this or place over free text
`page`	No
`size`	No
`sort`	No	photo = best photo first
`breed`	No	A breed name in any language, or its Wikidata id (Q39315)
`color`	No
`found`	No	Found pets (Vienna's list, announced for their owners for 30 days) are included by default, each marked found:true and NOT adoptable yet. exclude = adoptable pets only; only = found pets only. Never call a found pet adoptable
`limit`	No
`miles`	No	Radius in miles (default 50)
`photo`	No	good: only pets whose best photo passed our checks (analysed; not blurry, dark, tiny, or without a pet in it). Pets not analysed yet are left out
`place`	No	The same as near, as structured fields (do not put a street address or a whole sentence here; the server resolves it against its own place table)
`facets`	No	Add counts by species, size, age, sex, region and good-with
`region`	No	Taiwan county or city, e.g. Taipei City, New Taipei City, Taoyuan City
`country`	No	Which country's shelters: US, CA, TW (Taiwan), ES (Spain) or AT (Austria). Optional when near is a US ZIP or a Taiwan place
`species`	No
`good_with`	No	Only pets the rescue says are good with these
`min_photo_px`	No	Only pets whose best photo is at least this many pixels on its longest side

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 8, 2026

changedInput schema / properties / country / description

Previous value: -"Which country's shelters: US, CA or TW (Taiwan). Optional when near is a US ZIP or a Taiwan place"New value: +"Which country's shelters: US, CA, TW (Taiwan), ES (Spain) or AT (Austria). Optional when near is a US ZIP or a Taiwan place"

changedInput schema / properties / country / enum

Previous value: -[
-  "US",
-  "CA",
-  "TW"
-]New value: +[
+  "US",
+  "CA",
+  "TW",
+  "ES",
+  "AT"
+]

addedInput schema / properties / found

Added value: +{
+  "description": "Found pets (Vienna's list, announced for their owners for 30 days) are included by default, each marked found:true and NOT adoptable yet. exclude = adoptable pets only; only = found pets only. Never call a found pet adoptable",
+  "enum": [
+    "include",
+    "exclude",
+    "only"
+  ],
+  "type": "string"
+}

addedInput schema / properties / min_photo_px

Added value: +{
+  "description": "Only pets whose best photo is at least this many pixels on its longest side",
+  "maximum": 4000,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / photo

Added value: +{
+  "description": "good: only pets whose best photo passed our checks (analysed; not blurry, dark, tiny, or without a pet in it). Pets not analysed yet are left out",
+  "enum": [
+    "good"
+  ],
+  "type": "string"
+}

addedInput schema / properties / sort / description
```
Added value: +"photo = best photo first"
```

changedInput schema / properties / sort / enum

Previous value: -[
-  "relevance",
-  "newest",
-  "distance"
-]New value: +[
+  "relevance",
+  "newest",
+  "listed",
+  "distance",
+  "photo"
+]

changedInput schema / properties / species / enum

Previous value: -[
-  "Dog",
-  "Cat",
-  "Rabbit",
-  "Bird",
-  "Horse",
-  "Small animal",
-  "Reptile",
-  "Pig",
-  "Barnyard"
-]New value: +[
+  "Dog",
+  "Cat",
+  "Rabbit",
+  "Bird",
+  "Horse",
+  "Small pet",
+  "Reptile",
+  "Pig",
+  "Barnyard"
+]

First observedOct 7, 2026

TDQS

B3.2/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds genuine behavioral value beyond them: it discloses the response shape (interactive view vs. plain text list) and the fallback behavior for clients lacking interactive rendering, which the annotations do not convey. It still omits pagination and result-volume behavior for a 22-param search.

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, purpose front-loaded, with the interactive-view detail following. The middle sentence ('Use it when someone wants to look at pets to adopt') largely restates the purpose, a minor redundancy, but nothing is bloated.

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

Completeness3/5

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

For a 22-parameter, zero-required, nested-object search with no output schema, the description covers the output form well but leaves the sibling-routing question entirely open and says nothing about parameter interplay. It is minimally adequate rather than complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description contributes no parameter guidance at all despite 22 parameters. Schema coverage is 68%, below the high-coverage baseline threshold, and roughly a third of parameters (e.g. age, sex, size, page, limit, country, species) carry no schema description, so the description's silence leaves real gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource ('Show adoptable pets near a place') plus the output form (interactive view with photos, facts, and a meet button), which is more than a tautology. However, it never distinguishes itself from sibling find_pets or similar_pets, which plausibly return the same pet data, so an agent cannot tell which to pick from the text alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use it when someone wants to look at pets to adopt' gives only a generic trigger and names no alternatives, even though siblings find_pets, search_by_description and similar_pets exist. The 'apps without interactive views get the same list as text' line is a rendering fallback, not a when-to-use/when-not-to-use rule.

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

All Petnecto tools Inspect

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

Need Help?