Skip to main content
Glama

Ver configuração do Puxador

get_userbot_config
Read-only

Mostra a configuração do módulo Puxador deste bot: settings (grupo de aprovação, destino padrão, blocklist global, fonte padrão de texto/foto, publicação automática na Vitrine, status da sessão, aprovação automática — autoApprove, e se o aceite foi dado em autoApproveAcceptedAt/By — e approvalMode), canais monitorados (com perfil de formatação, substituições, palavras que descartam, destino próprio e autoApprove) e as regras de roteamento (com autoApprove). Use antes de alterar qualquer coisa, pra saber o estado atual.

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": "get_userbot_config"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
successNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

The readOnlyHint/destructiveHint annotations already establish the safety profile, and the description correctly stays consistent with them. What it adds is a field-level inventory of the configuration object, but that inventory largely duplicates what the output schema already exposes, so the incremental behavioral context is modest.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first clause, which is good, but the remainder is a single very long sentence with deeply nested parentheses enumerating fields (autoApprove, autoApproveAcceptedAt/By, approvalMode, per-channel formatting profiles...). Much of that detail is already available in the output schema, making the sentence heavier than the tool warrants.

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 zero-parameter read tool with full annotation coverage and an output schema, the description supplies all the caller needs: what the tool returns, that it is a state read, and when to call it. The field enumeration is partly redundant with the output schema, but nothing essential is missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. The description does not introduce any input concepts that could mislead, which keeps it at the baseline.

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?

Opens with a specific verb+resource ('Mostra a configuração do módulo Puxador deste bot') and then enumerates the three sections returned (settings, canais monitorados, regras de roteamento), so the agent knows exactly what data this yields versus broader tools like get_bot_info. It never names the sibling it complements, so differentiation is implied rather than stated.

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?

'Use antes de alterar qualquer coisa, pra saber o estado atual' gives a clear usage context and implicitly points at set_userbot_config as the follow-up action. It stops short of explicitly naming that alternative or stating exclusions, so it is a strong 4 rather than a 5.

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