WACrew

agenda_ver

Reads the operator’s Google Calendar across all calendars for a chosen date window, returning event IDs, calendar names, and Brasília times so events can be edited or deleted.

Instructions

Lê o Google Agenda do operador (todas as agendas da conta) numa janela de datas; padrão hoje até daqui a 7 dias. Cada evento traz agenda e id (use em agenda_editar/agenda_apagar) e hora_brt em horário de Brasília; organizador = reunião de outra pessoa, que só ela altera. Desconectado = erro pedindo para reconectar em /agenda no painel.

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

Input Schema

Name	Required	Description
`de`	No	início: YYYY-MM-DD ou data-hora ISO (sem fuso = Brasília)
`ate`	No	fim exclusivo: YYYY-MM-DD ou data-hora ISO; no máximo 62 dias depois de `de`
`agendas`	No	ids de agenda para filtrar; omitido = todas

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 14, 2026

TDQS

A4.3/5.0

Behavior4/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 well: it discloses that it reads all calendars, the default lookback/lookahead, the timezone of timestamps (`hora_brt`), and the important constraint that `organizador` events belong to someone else and only they can change them. It omits volume/pagination behavior and does not explicitly state it is read-only, which is only implied by "Lê".

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?

Four dense sentences with the primary action and default window front-loaded, followed by return-shape and error behavior. Nothing is redundant, though packing ids, timezone, organizer semantics and reconnect instructions into two sentences makes it slightly hard to scan.

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 no-annotation, no-output-schema read tool with 3 simple params, it covers purpose, defaults, key return fields, edit/delete handoff and the disconnected-account failure mode. Gaps remain around result volume limits and how all-day or multi-day events are represented.

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 the undocumented default for `de`/`ate` (hoje até daqui a 7 dias) which the schema does not state anywhere. The `agendas` filter, ISO format and 62-day cap remain schema-only, which is acceptable at this coverage.

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?

Opens with a specific verb+resource ("Lê o Google Agenda do operador") plus scope (todas as agendas da conta) and default window, which immediately separates it from agenda_marcar/agenda_editar/agenda_apagar named later.

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 the default date window so the agent knows it can call with no arguments, and points at agenda_editar/agenda_apagar for follow-up via the returned ids. It stops short of explicitly stating when NOT to use it (e.g. buscar for keyword search across the mailbox), so it's context-rich but not fully routing.

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