Skip to main content
Glama
Sign In

Adoteca — Adoção de Pets no Brasil

by br.com.adoteca
OverviewDiscussionsAdmin

Buscar ONGs e protetores na cidade

search_rescuers
Read-only

Use quando perguntarem QUAIS ONGs ou protetores existem em uma cidade. Lista quem tem pets no catálogo ali, com o link de cada um. Vem só de anúncios, que podem ser antigos: não é registro completo e não indica se a ONG está ativa nem se tem vaga para acolher.

Input Schema

NameRequiredDescriptionDefault
cityYesNome do MUNICÍPIO por extenso, ou o slug devolvido pela resolução de cidade. Obrigatório: a resposta é sempre de uma cidade. Se o nome for ambíguo ou ninguém tiver pets ali hoje, o erro diz o que fazer.
pageNoPágina, começando em 1.
limitNoQuantos resultados devolver por página. Valores acima de 24 são reduzidos a 24. Buscar por `name` devolve no máximo 5: é uma lista para confirmar, não para navegar.
stateNoSigla de duas letras da UF (SP, MG), se a pessoa informou. Opcional.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / $defs / AgentRescuerSummary / properties / contact_url
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Link para falar com a ONG: abre uma página da Adoteca que leva ao Instagram dela. Mostre este link ao indicar contato.",
+  "title": "Contact Url"
+}
    • changedOutput schema / $defs / AgentRescuerSummary / properties / instagram_url / description
      Previous value: -"Perfil oficial da ONG no Instagram."New value: +"Perfil oficial da ONG no Instagram. Para indicar contato, mostre contact_url."
  2. Changed1 schema field changed
    • changedOutput schema / $defs / AgentRescuerSummary / properties / short_code / description
      Previous value: -"Código curto da ONG (o mesmo de www.adoteca.com.br/o/{code})."New value: +"Código curto da ONG (o mesmo de adoteca.com.br/o/{code})."
  3. Changed1 schema field changed
    • changedOutput schema / $defs / AgentRescuerSummary / properties / short_code / description
      Previous value: -"Código curto da ONG (o mesmo de adoteca.com.br/o/{code})."New value: +"Código curto da ONG (o mesmo de www.adoteca.com.br/o/{code})."
  4. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  5. Changed2 schema fields changed
    • changedOutput schema / $defs / AgentRescuerSearchResponse / properties / note / description
      Previous value: -"Contexto obrigatório: a lista cobre só quem tem pets anunciados AGORA — não é um registro de todas as ONGs da cidade."New value: +"Contexto obrigatório: a lista cobre só quem tem pets anunciados no catálogo, de qualquer data — não é um registro de todas as ONGs da cidade, nem garantia de que estejam ativas hoje."
    • changedOutput schema / $defs / AgentRescuerSummary / properties / available_count / description
      Previous value: -"Pets disponíveis para adoção agora."New value: +"Pets com anúncio ativo para adoção. O anúncio pode ser antigo — não prometa à pessoa que é recente."
  6. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description goes well beyond them: it discloses the data source (listings only, possibly stale), and explicitly warns it is not a complete registry and does not indicate whether the NGO is active or has capacity. That is high-value context an agent needs to avoid over-claiming results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tightly-written sentences: trigger first, then what is returned (with links), then the sourcing caveat. Every sentence carries distinct, useful information with no 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?

An output schema exists, so return-shape explanation is unnecessary, and the annotations cover the safety profile. Combined with the description's coverage of purpose, source limitations, and invocation trigger, nothing material is missing for correct use.

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 all four parameters (city, page, limit, state) are already documented in the schema, including the 24-result cap and the 5-result cap for name search. The tool description adds no parameter-level meaning beyond the schema, so the baseline of 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?

States a specific verb and resource (list NGOs/rescuers for a city) plus the exact scope: only those who have pets in the catalog there. This implicitly distinguishes it from siblings like search_pets (finds pets) and get_rescuer_details (one rescuer's detail), so an agent can route correctly without opening schemas.

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?

Opens with an explicit trigger condition in caps ('Use quando perguntarem QUAIS ONGs ou protetores existem em uma cidade'), which is clear context for invocation. However, it names no alternatives or exclusions (e.g., when to prefer get_rescuer_details or search_pets instead), leaving that inference to the agent.

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

All Adoteca — Adoção de Pets no Brasil 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