Skip to main content
Glama

Histórico de atividade

activity_history
Read-only

Linha do tempo (mais recente primeiro) do que aconteceu: entradas/saídas por grupo (agregadas por hora), alertas de queda, grupos registrados, números WhatsApp adicionados/removidos/caídos, campanhas criadas/arquivadas e incidentes. Use para "o que aconteceu hoje/esta semana" ou para investigar um período. Padrão: últimos 30 dias. Datas (quando, de, ate) em ISO com o fuso de Brasília. Com has_more true, repita com offset = next_offset.

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": "activity_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
deNoOpcional. Início (padrão: 30 dias atrás). Data ISO (AAAA-MM-DD ou com hora e fuso) ou epoch em segundos.
ateNoOpcional. Fim (padrão: agora). Data ISO (AAAA-MM-DD ou com hora e fuso) ou epoch em segundos.
tipoNoOpcional. Só itens desse tipo.
limiteNoMáximo de itens (1 a 200; padrão 50).
offsetNoQuantos itens pular (0 = início). Para a próxima página, use o next_offset da resposta.
campanha_idNoOpcional. Só itens dessa campanha (id ou slug).

Output Schema

NameRequiredDescriptionDefault
deNoISO 8601 com o fuso de Brasília (-03:00).
ateNoISO 8601 com o fuso de Brasília (-03:00).
itensNoLinha do tempo, mais recente primeiro.
totalNoQuantos casaram com o filtro (todas as páginas).
successNo
has_moreNotrue quando há mais itens depois desta página.
next_offsetNooffset da próxima página; null na última.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description then adds genuinely useful behavioral detail the annotations don't: the output is ordered most-recent-first and pagination uses has_more with next_offset. It says nothing about result volume, rate limits, or what an empty window returns.

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?

The opening clause front-loads the resource and its ordering, then the event taxonomy, then usage, defaults, timezone and pagination. It's dense but every sentence adds information; the only wasted token is the stray "quando" reference.

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?

With an output schema present and full parameter coverage, the return format doesn't need explaining, and the description still covers ordering, default window, timezone and paging. The remaining gap is around how the filters interact (tipo vs campanha_id) and when to reach for a sibling instead.

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 description coverage is 100%, so the six parameters, enums and defaults are already documented and the baseline is 3. The description contributes only timezone semantics (Brasília time for de/ate) and the offset=next_offset paging loop, both of which largely restate what the schema says. The mention of "quando" doesn't map to any parameter in the schema.

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 names a concrete verb-resource pair (a reverse-chronological timeline of events) and enumerates the event families it covers: hourly-aggregated group joins/leaves, drop alerts, registered groups, WhatsApp numbers added/removed/dropped, campaigns created/archived, and incidents. That gives an agent a precise picture of the payload. It never names the close siblings activity_stats or get_userbot_history, so the separation between this tool and those two is left to inference.

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?

It gives clear trigger scenarios — "o que aconteceu hoje/esta semana" or investigating an arbitrary period — and states the default window of the last 30 days. What's missing is any when-not guidance: nothing tells the agent when to prefer activity_stats (aggregates) or get_userbot_history, even though those are the obvious alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources