Skip to main content
Glama
Sign In

Radar noEixo

by com.noeixodigital
OverviewDiscussionsAdmin

Create quick reply

create_quick_reply

⚡ MENSAGENS RÁPIDAS — Cria uma mensagem rápida do Chat. Por padrão é DA EQUIPE (toda a conta vê ao digitar "/"); da_equipe="false" deixa pessoal. Texto livre, sem aprovação da Meta — só pode ser enviada com a janela de 24h aberta. O título aparece na lista e filtra a busca depois da "/".

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": {
      "title": "<title>",
      "content": "<content>"
    },
    "name": "create_quick_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
grupoNoGrupo no menu do "/" (até 30 caracteres), ex.: "Objeções". "" tira do grupo.
ordemNoPosição dentro do grupo (1 a 999). Sem posição, vai para o fim do grupo, em ordem alfabética.
titleYesRótulo curto exibido na lista (até 60 caracteres). Ex.: "Saudação", "Pedir cidade".
contentYesTexto inserido no campo de mensagem (até 4000 caracteres). O operador pode editar antes de enviar. Use {nome} para o primeiro nome do cliente e {empresa} para o nome do negócio: são trocados ao inserir.
da_equipeNo"true" (padrão): toda a conta vê. "false": só o dono da chave.
target_user_idNoID da conta-alvo (opcional; APENAS o admin da plataforma pode usar). Padrão: a conta autenticada.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false/openWorldHint=false/destructiveHint=false, which says it is a safe write. The description adds real behavioral context: the default scope is account-wide visibility, setting da_equipe=false narrows it to the key owner, content requires no Meta approval, and the reply can only be sent with the 24h window open. These disclosure points go well beyond the annotations.

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?

Front-loaded with a category marker and a single direct verb+resource sentence, followed by the most decision-relevant defaults (team vs personal). Only the 24h-window send note is slightly tangential, but it still earns its place as operational context.

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 6-param create tool with full schema coverage and intact annotations, the description covers purpose, defaults, visibility, and the sending constraint well. It does not say what the response contains (e.g., the created ID), which is a minor gap given there is no output schema.

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% and each property already has a detailed description, so the schema carries most of the weight. The description mainly reinforces da_equipe's default team behavior and notes that the title appears in the list and filters the "/" search, adding only marginal meaning beyond the schema.

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 verb 'Cria' plus the resource 'mensagem rápida do Chat' make the action and object immediately clear. It does not explicitly name siblings like update_quick_reply or list_quick_replies, but the create-vs-read-vs-modify distinction is obvious from the name and framing.

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?

The description gives useful context (default team-wide, da_equipe=false for personal, 24h window sending constraint) but never explicitly states when to reach for this versus update_quick_reply, list_quick_replies, or delete_quick_reply. Usage is implied by the operation rather than spelled out.

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

All Radar noEixo toolsInspect
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