Skip to main content
Glama

List follow ups

list_follow_ups
Read-only

Lista os retornos (data combinada para voltar a falar com o cliente, ex.: "me procura em junho"). Padrão: os marcados de hoje para trás (atrasados e de hoje) e dos próximos 7 dias. situacao: marcado (padrão), sugerido (o agente percebeu o pedido na conversa e espera alguém confirmar com confirm=true em update_follow_up) ou todos_abertos. Com hoje=true: os atrasados e os de hoje (a lista "Retornos de hoje" da tela de Conversas), com resumo do dia e mensagem sugerida. Também aceita contact_id ou phone para ver o retorno de um contato.

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

Input Schema

NameRequiredDescriptionDefault
ateNoAté que dia (AAAA-MM-DD, Brasília). Padrão: daqui a 7 dias.
hojeNotrue = só atrasados e de hoje (fim do dia em Brasília). Ignora ate.
phoneNoAlternativa a contact_id.
situacaoNoPadrão: marcado.
contact_idNoRetornos abertos de um contato.
responsavel_idNoSó de quem retorna (id de list_team_permissions). Omitido = todos da conta.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / hoje
      Added value: +{
      +  "description": "true = só atrasados e de hoje (fim do dia em Brasília). Ignora ate.",
      +  "type": "boolean"
      +}
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that: it discloses what the default result set contains, that hoje=true yields a day summary plus a suggested message, and that hoje overrides ate. No pagination or rate-limit behavior is mentioned, but no schema parameter implies either.

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?

Purpose and default behavior are front-loaded in the first two clauses, and every following sentence adds a distinct mode or default rather than padding. It is dense single-paragraph prose with nested parentheses, which is slightly harder to scan than a bulleted mode list, but no sentence is wasted.

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 no output schema and six optional parameters, the description carries the burden well: it covers defaults, each filter mode, and hints at what the hoje response includes. Gaps are minor — nothing about result ordering, volume limits, or what fields each follow-up record contains.

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; the description rises above it by explaining interactions the schema does not: hoje ignores ate, and "sugerido" means the agent inferred the request from a conversation and awaits confirmation. The contact_id/phone alternation is restated from the schema rather than extended, which keeps this from being a 5.

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 precise verb+resource ("Lista os retornos") and defines the domain object inline with a concrete example ("me procura em junho"), so an agent unfamiliar with the term still understands what is being listed. It also disambiguates the three states a follow-up can be in, which a bare name would not.

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?

States the default window (overdue + today + next 7 days) and explains when each mode applies: hoje=true for the day view, contact_id/phone for a single contact, situacao for confirmed vs agent-detected items. It even routes the confirm path to "confirm=true em update_follow_up". It stops short of saying when not to use this tool (e.g. use create_follow_up to add one), so it falls just below a full 5.

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