Skip to main content
Glama

Configurar bot

configurar_bot
Destructive

Edita bot, memória ou gravação. Só administrador. Exige sessão do painel, com CSRF nas escritas; chave de API não basta. Só dono ou administrador da organização. Apenas a permissão de conexão pode mudar com tarefa em curso. Gravação também controla a captura de auditoria destas chamadas. Desligar a gravação remove a cópia salva do módulo; não expurga auditorias anteriores. A política das outras rotas /v1/* não muda.

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": {
      "acao": "<acao>"
    },
    "name": "configurar_bot"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoEm bot: id existente para editar; omita para criar, até quatro. Em remover: id do bot a excluir, exceto o último do espaço.
acaoYesbot, remover, memoria, gravacao ou integracoes.
nomeNoEm bot: nome de 1 a 60 caracteres.
ativoNoEm integracoes: permite acesso às conversas pelas chaves desta organização.
textoNoEm memoria: até 4.000 caracteres; vazio apaga as notas.
gravarNoEm gravacao: true salva cifrado, false mantém somente em RAM.
modeloNoEm bot: id rota/*, exceto rota/local nesta versão.
instrucaoNoEm bot: instruções de 1 a 2.000 caracteres.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the destructiveHint=true annotation by spelling out what is destroyed: disabling recording removes the module's stored copy but does not purge prior audit records. It also discloses the audit side-effect of the recording setting, the auth/CSRF model, and that other /v1/* route policy is unaffected — exactly the context annotations cannot carry.

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?

Purpose and the strongest constraint (admin/CSRF) are front-loaded, then consequences follow. Sentences are telegraphic and mostly earn their place; the closing note on other /v1/* routes is useful scope-limiting but borders on tangential.

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 an eight-parameter destructive admin tool with no output schema, the description covers authorization, transport security, in-flight editing limits, and destruction/retention semantics. An agent has enough to decide whether it may call this and what will be lost; the only residual gap is idempotency, which the annotations already flag as false.

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 description coverage is 100%, with per-parameter conditional semantics already documented (id creates vs. edits vs. deletes, texto empty clears notes, gravar encrypted vs. RAM). The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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?

States a concrete verb and resource set ('Edita bot, memória ou gravação'), so an agent immediately knows this is a configuration mutation tool. However, it omits two of the five enum modes — 'remover' (deletion) and 'integracoes' — which are only discoverable from the schema, so the destructive delete path is invisible in prose.

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?

Gives unusually explicit invocation prerequisites: administrator only, panel session with CSRF required for writes, API key insufficient, owner or org-admin role. It also states the constraint that only connection permission may change while a task is running. What it lacks is routing guidance against siblings — notably it never distinguishes the 'memoria' action from atualizar_memoria_bots, nor 'remover' from cancelar_bot or consultar_bots.

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