Radar noEixo

Update quick reply

update_quick_reply

DestructiveIdempotent

⚡ MENSAGENS RÁPIDAS — Altera título, texto ou o tipo (da equipe/pessoal) de uma mensagem rápida. Pessoal só o autor altera; da equipe, o autor, o gerente ou o dono. Campos omitidos ficam como estão.

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>"
    },
    "name": "update_quick_reply"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	ID da mensagem rápida (de list_quick_replies)
`grupo`	No	Grupo no menu do "/" (até 30 caracteres), ex.: "Objeções". "" tira do grupo.
`ordem`	No	Posição dentro do grupo (1 a 999). Sem posição, vai para o fim do grupo, em ordem alfabética.
`title`	No	Novo título (opcional)
`content`	No	Novo texto (opcional). Aceita {nome} e {empresa}.
`da_equipe`	No	Opcional: "true" compartilha com a equipe, "false" torna pessoal.
`target_user_id`	No	ID da conta-alvo (opcional; APENAS o admin da plataforma pode usar). Padrão: a conta autenticada.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false. The description adds meaningful context beyond annotations by explaining partial-update behavior ('Campos omitidos ficam como estão') and role-based edit permissions, though it does not discuss irreversibility or side effects in more detail.

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?

The description is front-loaded with the resource label and operation, then gives permission and partial-update details in tight sentences. Every sentence contributes useful information without redundant restatement.

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?

Given the complete input schema, mutation annotations, and absence of an output schema, the description supplies enough operational context: scope, editable fields, permissions, and partial-update behavior. It does not need to document return values, and parameter specifics are covered by the schema.

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 description coverage is 100%, so all seven parameters are already documented. The description adds useful general patch semantics that omitted fields remain unchanged and identifies title/text/type as the editable content, while leaving grupo, ordem, and target_user_id details to the schema.

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, 'Altera', and resource, 'mensagem rápida', and names the updatable fields (título, texto, tipo) with team/personal scope. This clearly distinguishes the update operation from siblings such as create_quick_reply, delete_quick_reply, and list_quick_replies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides authorization context: personal quick replies can only be changed by the author, while team quick replies can be changed by the author, manager, or owner. However, it does not explicitly say when to choose this tool over create/delete/list alternatives, nor does it mention prerequisites such as obtaining the id from list_quick_replies.

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

All Radar noEixo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?