Skip to main content
Glama

Adoteca — Adoção de Pets no Brasil

by br.com.adoteca

Montar link do catálogo

get_catalog_link
Read-only

Monta o link do catálogo com os filtros pedidos e confirma que existem pets neles. Use quando a pessoa quiser ver a lista no site. Se url vier null, não há link: leia note e ofereça tirar um filtro. Nunca escreva um link de catálogo à mão.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ageNoFaixa etária, uma só: 'filhote', 'adulto' ou 'idoso'. São as três faixas que o catálogo distingue; os cortes mudam com espécie e porte (idoso a partir de 8 anos no cão grande, 9 no médio, 10 no pequeno e no gato).
sexNoSexo: 'male'/'macho' ou 'female'/'femea'.
cityNoNome do MUNICÍPIO por extenso, não do bairro nem abreviado: 'Belo Horizonte', não 'BH'. Acento é opcional. Se o nome for ambíguo, ou se nenhuma ONG tiver pets ali hoje, o erro explica o que fazer — leia e siga; não significa que a cidade não exista.
sizeNoPortes, um ou mais: 'small'/'pequeno', 'medium'/'medio', 'large'/'grande'. Envie os dois quando a pessoa aceitar os dois.
sortNoOrdem da página: 'recentes' (padrão, os anúncios mais novos primeiro) ou 'disponiveis' (os que ainda estão para adoção primeiro, empurrando os já adotados para o fim).
breedNoRaça: slug ('golden-retriever') ou nome em português ('pastor alemão'). A maioria do catálogo é SRD (sem raça definida). Use a listagem de raças para ver as raças com pets hoje.
stateNoSigla de duas letras da UF (SP, MG), apenas para desambiguar `city`. Busca só por estado NÃO é suportada: sempre envie `city` junto.
speciesNoEspécie: 'dog'/'cachorro' ou 'cat'/'gato'.
neuteredNotrue devolve somente pets castrados. `false` é IGNORADO pelo mesmo motivo de `vaccinated`; leia `neutered` na ficha do pet.
vaccinatedNotrue devolve somente pets vacinados. `false` é IGNORADO: a maioria dos anúncios não informa vacinação, então filtrar por 'não vacinado' esconderia quase todo o catálogo. Para saber de um pet específico, leia `vaccinated` na ficha (null = a ONG não informou).
special_needsNotrue monta o link só com pets com cuidados especiais. `false` é IGNORADO: o catálogo não tem o filtro inverso.
good_with_catsNoSomente pets que convivem bem com gatos.
good_with_dogsNoSomente pets que convivem bem com cães.
good_with_kidsNoSomente pets que convivem bem com crianças.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.5/5.0
Behavior5/5

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

The description adds meaningful behavioral detail beyond the read-only annotation: it explains that if `url` comes back null, there is no link and the agent should read `note` and suggest removing a filter. It also warns 'Nunca escreva um link de catálogo à mão,' which prevents a common misuse.

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?

Four short, purposeful sentences with no filler. The core purpose is front-loaded, followed by usage context, error handling, and a critical constraint. Every sentence earns its place.

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?

For a read-only link-building tool with full schema coverage and an output schema, the description covers what matters: when to use it, what the null-url behavior is, and a key anti-manual-link constraint. Nothing necessary for an agent to call it correctly seems 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?

The input schema covers 100% of the parameters, so the baseline is 3. The description only refers generally to 'os filtros pedidos' and does not add parameter-specific meaning, but that is acceptable because every parameter already has a detailed description in the 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?

The description uses a specific verb ('Monta') and resource ('link do catálogo') and clearly states the tool's core function: build a catalog link with requested filters and verify pets exist under those filters. It also distinguishes itself by mentioning the null-url case and warning against hand-writing links, which makes the tool's responsibility unambiguous.

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?

The description explicitly says to use this tool when the person wants to see the list on the site, which gives a clear triggering context. It does not explicitly name alternatives or exclusions, but given the sibling tools are mostly search/detail tools rather than link builders, the usage context is strong enough.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool clearly targets a distinct action and resource: catalog link building, city stats, pet details, rescuer details, breed listing, city resolution, guides, pet search, rescuer search, and similar pets. There is no meaningful overlap; even search_pets and search_similar_pets are differentiated by scope (general vs. specific pet).

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case: get_* for details, search_* for queries, and list_breeds. This makes the API predictable and easy to navigate.

Tool Count5/5

10 tools is well-scoped for a pet adoption assistant. It covers browsing, searching, detailed views, statistics, guides, and URL generation without unnecessary bloat or overwhelming the agent.

Completeness4/5

The tool surface covers the main user journeys: searching pets, retrieving details, finding rescuers, getting city stats, and accessing guides. Minor gaps exist, such as no way to list all cities or directly initiate an adoption, but these are not critical for an informational assistant.

Resources