Skip to main content
Glama
Sign In

Adoteca — Adoção de Pets no Brasil

by br.com.adoteca
OverviewDiscussionsAdmin

Encontrar a cidade no catálogo

search_cities
Read-only

Converte o nome de uma cidade (com ou sem acento, com erro de grafia) no slug oficial do catálogo, com a UF. Use quando a pessoa citar uma cidade. ambiguous vem true quando o nome existe em mais de um estado. Não traz os números da cidade.

Input Schema

NameRequiredDescriptionDefault
cityYesNome do município como a pessoa escreveu, ex.: 'sao paulo', 'Cachoeirinha'.
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. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed1 schema field changed
    • changedOutput schema / $defs / AgentCityMatch / properties / pet_count / description
      Previous value: -"Pets anunciados nessa cidade nos últimos 90 dias. Inclui os já adotados, então pode ser maior que o número disponível agora."New value: +"Pets já anunciados nessa cidade, de qualquer data. Inclui os já adotados e anúncios antigos, então pode ser bem maior que o número disponível agora. Não prometa à pessoa que são recentes."
  3. Changed3 schema fields changed
    • removedOutput schema / $defs / AgentCityMatch / properties / ngo_count
      Removed value: -{
-  "description": "ONGs e protetores com pets anunciados nessa cidade.",
-  "title": "Ngo Count",
-  "type": "integer"
-}
    • addedOutput schema / $defs / AgentCityMatch / properties / rescuer_count
      Added value: +{
+  "description": "ONGs e protetores com pets anunciados nessa cidade.",
+  "title": "Rescuer Count",
+  "type": "integer"
+}
    • changedOutput schema / $defs / AgentCityMatch / required
      Previous value: -[
-  "slug",
-  "name",
-  "state",
-  "pet_count",
-  "ngo_count"
-]New value: +[
+  "slug",
+  "name",
+  "state",
+  "pet_count",
+  "rescuer_count"
+]
  4. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only cover the safety profile (readOnly, openWorld, non-destructive), and the description adds genuinely new behavior: fuzzy/accent-insensitive matching, the meaning of the `ambiguous` flag when a name spans multiple states, and the explicit statement that city statistics are not returned. It does not discuss latency, rate limits, or result ordering, so it falls short of a 5.

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 tight sentences, front-loaded with the core input→output transformation, then usage, then the caveat. Every sentence carries distinct information with no padding.

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 an output schema present, return values need not be enumerated, and the description still flags the `ambiguous` field and the exclusion of city statistics. Purpose, trigger, tolerance, and scope limits are all covered for a two-parameter lookup tool.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning about the `city` input: it accepts unaccented forms and misspellings, which the schema example ('sao paulo') only hints at. The `state` parameter receives no extra semantic treatment beyond 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?

States a concrete transformation: converts a city name into the official catalog slug plus UF, explicitly tolerating accents and typos. It also distinguishes itself from data-bearing siblings with 'Não traz os números da cidade', so an agent can separate it from get_city_stats without opening a 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 quando a pessoa citar uma cidade' gives a clear triggering condition, and the closing sentence carves out what this tool is not for. It stops short of naming the alternative tool (e.g. get_city_stats) that should be used when numbers are wanted, so the routing is implied rather than explicit.

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