Skip to main content
Glama
Sign In
WACrew

WACrew

by sumioshi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

listar_grupos

Lists collected WhatsApp groups with slug, name, message count, and last message date so you can reference each slug in other tools.

Instructions

Lista os grupos coletados (slug, nome, nº de mensagens, data da última). Use o slug nas outras ferramentas.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listar_grupos"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 behavioral burden. The word "Lista" implies a read-only operation, but the description does not explicitly state safety, auth, pagination, ordering, or whether all groups are returned.

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?

The description is compact and front-loaded: it first states what is listed and what fields are returned, then adds the key follow-up instruction about the slug. Every sentence adds value.

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 zero-parameter listing tool with no output schema, the description is mostly complete because it names the returned fields and explains the main use of the result. Minor gaps remain around pagination and ordering, but the tool's low complexity keeps this adequate.

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?

The tool has zero input parameters, so parameter semantics are largely not applicable. The description still usefully clarifies that returned slugs are meant to be reused in other tools.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it lists collected groups and names the returned fields (slug, name, message count, last date). It is clear what the tool does, though it does not explicitly distinguish itself from sibling list or group-management tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage guidance is to use the returned slug in other tools, which implies this tool is a discovery step. It does not state when to call this versus other listing tools or group-related actions, and it provides no explicit exclusions.

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

Deploy Server

Other Tools