WACrew

ver_imagem

Shows a WhatsApp group image, screenshot, or sticker to the AI for visual understanding, or retrieves the latest group image when no media path is provided.

Instructions

Mostra de fato uma imagem (print/screenshot/sticker) de um grupo para a IA enxergar. Use quando precisar entender o conteúdo visual — ex.: print de um bug que o cliente mandou. Sem mediaPath, mostra a ÚLTIMA imagem/figurinha do grupo (atalho pra 'vê a imagem que acabou de chegar', sem precisar de ler_mensagens antes).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "grupo": "<grupo>"
    },
    "name": "ver_imagem"
  }
}

Input Schema

Name	Required	Description	Default
`grupo`	Yes	slug do grupo
`mediaPath`	No	mediaPath da mensagem (campo 'midia'); ausente = última imagem/figurinha do grupo

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 14, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description carries the full burden and does disclose useful behavior: the tool returns viewable image content ('para a IA enxergar') and defaults to the last image/sticker when mediaPath is omitted. It says nothing about failure behavior when no image exists, any permission/scope requirements, rate limits, or the mediaPath source format.

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?

Front-loaded with the core action, then usage guidance, then the default-behavior shortcut — each of the three sentences carries distinct information. The parenthetical asides are slightly chatty but not wasteful.

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

Completeness4/5

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

For a simple two-parameter read tool with no annotations and no output schema, the description covers what is returned (visible image content), when to reach for it, and the default path. Only edge-case behavior (no image available) and any access constraints are missing, which is a modest gap at this complexity.

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 coverage is 100%, with both parameters already documented in the input schema, so a baseline of 3 applies. The description reinforces the mediaPath-absent fallback, which is helpful but already present in the schema field description; it adds no new format or constraint details for grupo.

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 verb and resource — it actually displays an image (screenshot/sticker) from a group so the AI can see it. It also implicitly separates itself from message-reading tools by noting no prior ler_mensagens call is needed, and from ver_video by naming images/stickers as its target.

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?

Gives an explicit trigger ('use when you need to understand visual content') with a concrete example (a client-sent bug screenshot) and explains the no-mediaPath shortcut as an alternative to reading messages first. It lacks any explicit when-not guidance or prerequisites, so it falls short of a full 5.

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