get_rescuer_detailsFicha de uma ONG ou protetor: cidades atendidas, contatos, site e página de doação (donation_url). Aceita o código curto do link ou o @ do Instagram da ONG. Não traz chave PIX.
| Name | Required | Description | Default |
|---|---|---|---|
| rescuer_ref | Yes | Código curto da ONG (ex.: 'ab12cd', o mesmo de adoteca.com.br/o/{code}) ou o @ do Instagram dela, sem arroba. |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
Output schema / $defs / AgentRescuerDetail / properties / contact_urlAdded 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"
+}Output schema / $defs / AgentRescuerDetail / properties / instagram_url / descriptionPrevious value: -"Perfil oficial da ONG no Instagram."New value: +"Perfil oficial da ONG no Instagram. Para indicar contato, mostre contact_url."Input schema / properties / rescuer_ref / descriptionPrevious value: -"Código curto da ONG (ex.: 'ab12cd', o mesmo de www.adoteca.com.br/o/{code}) ou o @ do Instagram dela, sem arroba."New value: +"Código curto da ONG (ex.: 'ab12cd', o mesmo de adoteca.com.br/o/{code}) ou o @ do Instagram dela, sem arroba."Output schema / $defs / AgentRescuerDetail / properties / short_code / descriptionPrevious 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})."Input schema / properties / rescuer_ref / descriptionPrevious value: -"Código curto da ONG (ex.: 'ab12cd', o mesmo de adoteca.com.br/o/{code}) ou o @ do Instagram dela, sem arroba."New value: +"Código curto da ONG (ex.: 'ab12cd', o mesmo de www.adoteca.com.br/o/{code}) ou o @ do Instagram dela, sem arroba."Output schema / $defs / AgentRescuerDetail / properties / short_code / descriptionPrevious 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})."Input schema / additionalPropertiesAdded value: +falseOutput schema / $defs / AgentRescuerDetail / properties / available_count / descriptionPrevious 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."Output schema / $defs / AgentRescuerDetail / descriptionPrevious value: -"The summary PLUS the fields a person needs before contacting an ONG.\n\nDeliberately NOT everything `account_to_detail` carries: `pix_key`, `cnpj`\nand `like_count` are excluded (as is `display_name`, which only the admin\nmapper emits) — see `agent_rescuer_detail`."New value: +"The summary PLUS the fields a person needs before contacting an ONG.\n\nDeliberately NOT everything `account_to_detail` carries: `pix_key` and\n`like_count` are excluded (as is `display_name`, which only the admin\nmapper emits) — see `agent_rescuer_detail`."Output schema / $defs / AgentRescuerDetail / properties / cnpjAdded value: +{
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "CNPJ da ONG, quando é uma entidade registrada. É um sinal de confiança, não um dado administrativo: antes de doar, a pessoa deve conferir se o nome que aparece na tela do PIX bate com este CNPJ. 14 dígitos, sem pontuação.",
+ "title": "Cnpj"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds a meaningful exclusion (no PIX key) which is useful behavioral context, but doesn't cover auth, rate limits, or error behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, front-loaded with the resource and its return fields, then input formats, then the PIX exclusion. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Output schema exists so return values needn't be explained, and the description still names key fields and the PIX caveat. An agent has enough to call it correctly, though a pointer to search_rescuers for discovery would complete the picture.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the schema description already explains rescuer_ref with an example. The description reinforces the two accepted formats (short code or Instagram @, no arroba), adding slight value beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (retrieve profile) and resource (NGO/protector), and enumerates the fields returned: cities served, contacts, site, and donation_url. It also distinguishes itself from siblings like search_rescuers by being a single-record detail lookup.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied by the input format (short code or Instagram handle) and by the sibling name search_rescuers, but the description never says when to use this versus search_rescuers. The negative note about PIX hints at what it does not cover without naming alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.