Skip to main content
Glama

Update follow up

update_follow_up
DestructiveIdempotent

Muda um retorno: acao=concluir (feito, sem enviar nada), adiar (nova data em dia/hora; pode trocar motivo e responsável), cancelar, confirmar (aceita a sugestão do agente, com ajustes opcionais) ou ignorar (descarta a sugestão do agente). id vem de list_follow_ups.

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": {
      "id": "<id>",
      "acao": "<acao>"
    },
    "name": "update_follow_up"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesID do retorno.
diaNoNova data (adiar/confirmar), AAAA-MM-DD.
acaoYesO que fazer.
horaNoHH:MM (Brasília).
motivoNoNovo motivo (opcional).
responsavel_idNoNovo responsável (opcional).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is partly covered. The description adds real context by clarifying that concluir sends nothing and ignorar discards the agent's suggestion, but it never says which actions are irreversible or what cancelar actually destroys, leaving the destructiveHint unexplained.

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?

A single dense sentence that front-loads the verb and the action list, with the id provenance appended last. Every clause carries information, though the run-on structure with nested parentheses makes it slightly harder to scan than a short bulleted list would.

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 six-parameter mutation tool with no output schema, the description covers the action space and parameter applicability well. It stops short of describing what confirmar produces (whether a message is sent or a record is created) and what the response looks like, which matters given destructiveHint=true.

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, and the description goes beyond it by mapping parameters to actions: dia/hora apply to adiar and confirmar, motivo and responsavel_id are optional overrides, and id comes from list_follow_ups. That action-to-parameter mapping is meaning the schema alone does not convey.

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?

States a specific verb (change a follow-up) and enumerates the five possible actions with a one-word gloss for each, so an agent knows exactly what the tool does. It also names the sibling list_follow_ups as the source of the id, which separates it from the read-side tool.

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?

Each action carries its own usage condition: concluir means done with nothing sent, adiar requires a new dia/hora, confirmar accepts the agent's suggestion with optional adjustments, ignorar discards it. What is missing is an explicit statement of when not to use this tool or which sibling to prefer for adjacent operations.

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