Skip to main content
Glama

Testar regras de canal

preview_userbot_rules
Read-only

Aplica um perfil de texto + substituições/bloqueios a um texto de exemplo e devolve o resultado, SEM salvar nada. Diz também se a mensagem seria descartada. O perfil só trata o texto; esta prévia não converte links nem escolhe Rotas/Plugins. Use pra validar as regras antes de gravar com set_userbot_config — o texto de exemplo pode vir do get_userbot_history.

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": {
      "text": "<text>"
    },
    "name": "preview_userbot_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesTexto de exemplo (o cru que chegaria do canal).
rulesNoRegras a testar: { converter, replacements, discardIfContains }. converter vazio = nenhum/genérico.

Output Schema

NameRequiredDescriptionDefault
successNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Adds context beyond the annotations: 'SEM salvar nada' makes the side-effect-free contract unambiguous and it discloses that the output also reports whether the message would be discarded. The scope carve-out (text only, no link conversion) prevents an agent from assuming full pipeline parity with the real config.

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?

Roughly four short sentences, front-loaded with what happens, then the scope limitation, then the sibling hand-off. No filler or restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only nested-object tool with an output schema and full annotation coverage, the description supplies everything an agent needs: what is applied, that nothing is persisted, that discard is reported, and which sibling to use to save. Return values are not re-explained, appropriately deferring to the output 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 coverage is 100% and the rules object is self-describing, so the baseline is 3. The description adds real meaning by implying that replacements and discardIfContains are what get exercised, and by warning that converter does not perform link conversion in preview — a caveat the schema's enum listing 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 concrete verb chain (applies text profile + replacements/blocks to a sample text, returns the result, flags discard) and explicitly scopes it to text-only, ruling out link conversion and Routes/Plugins. Distinct from siblings like set_userbot_config and convert_links without needing the schema.

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?

Explicit when-to-use: 'Use pra validar as regras antes de gravar com set_userbot_config', plus where the sample text comes from (get_userbot_history). It also names what the preview does NOT do (no link conversion, no Route/Plugin selection), which is an effective exclusion clause pointing to convert_links.

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