Skip to main content
Glama

Aprovar oferta do Puxador

approve_userbot_offer
Destructive

PUBLICA a oferta nos canais de destino (os "destinos" de list_userbot_queue), para todos os membros, e não dá para desfazer pelo MCP. Antes, mostre ao usuário o texto e os destinos e só aprove com um OK explícito dele nesta conversa. Só vale para oferta PENDING; repostagem da mesma oferta em 2 h é recusada. Exige dono ou admin do bot.

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": {
      "id": "<id>"
    },
    "name": "approve_userbot_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId da oferta (list_userbot_queue).
use_api_textNoOpcional. true publica o texto da versão API (versao_api.texto); false, o da origem. Ausente = padrão do canal.
use_api_photoNoOpcional. true publica a foto da versão API. Ausente = padrão do canal.

Output Schema

NameRequiredDescriptionDefault
idNo
na_filaNotrue quando a publicação ficou na fila do Puxador.
successNo
mensagem_idNo
publicado_emNoDestino onde a oferta saiu.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Adds substantial context beyond annotations: the action cannot be undone via MCP, it publishes to all members of destination channels, the 2h repost restriction, PENDING-only constraint, and owner/admin requirement. Annotations already flag destructive/irreversible, but the description fills in the operational consequences.

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?

Front-loaded with the critical action verb in caps, followed by a tight sequence of constraints, safety checks, and authorization rules. Every sentence carries safety-critical or operational information.

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?

Covers preconditions, side effects, irreversibility, authorization, and timing restrictions; an output schema exists so return values needn't be explained. Nothing an agent needs to call this safely is missing.

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%, so the schema already documents all three parameters, including the optional use_api_text and use_api_photo flags. The description adds no syntax or format details beyond what the schema provides, so 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 ('PUBLICA') and resource (oferta) with scope (canais de destino, todos os membros) and references the sibling list_userbot_queue as the source of destinations. It implicitly contrasts with reject_userbot_offer by defining the approval/publish action.

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 preconditions: only for PENDING offers, requires explicit user OK in the same conversation, and reposting within 2h is refused. Also names required authorization (owner or bot admin). This tells the agent exactly when to call and when not to.

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