Skip to main content
Glama

Create follow up

create_follow_up

Marca um retorno com um contato: no dia, quem retorna recebe o aviso (celular e WhatsApp da equipe) e encontra o resumo da conversa e a mensagem sugerida prontos. Não envia nada ao cliente. Um retorno aberto por contato: marcar outro substitui o atual. Dia em que a equipe não atende passa para o próximo dia de atendimento.

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": {
      "dia": "<dia>",
      "motivo": "<motivo>"
    },
    "name": "create_follow_up"
  }
}

Input Schema

NameRequiredDescriptionDefault
diaYesDia do retorno, AAAA-MM-DD (Brasília).
horaNoHH:MM (Brasília). Padrão 09:00.
phoneNoTelefone do contato, só dígitos com DDI.
motivoYesO que retomar e por quê, em uma frase (até 200 caracteres).
contact_idNoID do contato. Alternativa: phone.
responsavel_idNoQuem retorna (id de list_team_permissions). Padrão: quem está usando a chave.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only say readOnly=false, destructive=false, openWorld=false; the description adds substantive behavior the agent cannot infer: nothing is sent to the client, the responsible party is notified on team mobile and WhatsApp with the summary and suggested message, and a second creation silently substitutes the existing open follow-up. That substitution rule is exactly the kind of side effect an agent must know before calling.

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?

Three dense sentences, front-loaded with what the tool does, followed by the notification side effect, the replacement rule, and the business-day rule. Every sentence carries information an agent needs; nothing is padding.

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 creation tool with no output schema, the description covers the important behavior: who is notified, that the client is not contacted, the one-open-return constraint, and the business-day rollover. It does not state what the call returns (e.g. the new follow-up id) or any permission requirement, which leaves a small gap.

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%, so parameter documentation is already complete (dia format, hora default 09:00, phone vs contact_id alternative, responsavel_id default). The description adds one genuinely new semantic rule — a day when the team does not work rolls forward to the next business day — which deepens the meaning of 'dia' but covers nothing else.

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 opens with a specific verb+resource: 'Marca um retorno com um contato', and explains the effect (the responsible person gets a phone/WhatsApp notice plus conversation summary and suggested message). It is clearly distinct from list_follow_ups or update_follow_up, though it never names a sibling explicitly to sharpen the boundary.

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 real usage context: this is for scheduling a return, one open return per contact, and marking a new one replaces the current one — a rule that tells the agent when to prefer this over updating the existing record. It stops short of naming update_follow_up or list_follow_ups as the alternative path.

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