Radar noEixo

List quick replies

list_quick_replies

Read-only

⚡ MENSAGENS RÁPIDAS — Lista as mensagens rápidas do Chat (as que o operador insere digitando "/" no campo de mensagem): as pessoais da conta + as da equipe. Servem só com a janela de 24h ABERTA (texto livre); para janela fechada use templates (list_whatsapp_templates).

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_quick_replies"
  }
}

Input Schema

Name	Required	Description	Default
`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.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false). The description adds genuinely useful context beyond that: the 24h-window constraint and that the result merges personal plus team quick replies, while the schema flags that target_user_id is admin-only. Minor gaps: no mention of ordering or result size.

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 the verb and resource, followed by the definition and the window constraint. Slightly verbose with emoji and full-caps emphasis, but every sentence, including the template cross-reference, earns its place.

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 read-only list tool with no output schema, the definition supplies what matters: what is returned, the eligibility window, and where to go otherwise. Only return-format/pagination details are absent, which is acceptable here.

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 the single optional parameter already documents its default and admin-only restriction. The description adds nothing about target_user_id, so the baseline 3 applies.

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 and resource (list quick replies) and defines what they are: quick messages the operator inserts by typing '/' in the message field, covering both personal and team entries. This makes it clearly distinguishable from list_whatsapp_templates in the sibling set.

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

Usage Guidelines5/5

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

Explicitly states the condition for use — free text requires the 24h window to be OPEN — and names the alternative for the closed-window case: list_whatsapp_templates. The agent is routed without inference.

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?