Skip to main content
Glama

Histórico de conversões do Puxador

get_userbot_history
Read-only

Últimas ofertas capturadas pelo Puxador, com o texto CRU que chegou do canal e o texto FINAL depois das regras e da conversão de links (antes → depois), status, destino e quem decidiu. Use como exemplo real pra ajustar as regras de um canal, ou pra investigar por que uma oferta saiu de um jeito. Mais recentes primeiro; com has_more true, repita com offset = next_offset para as anteriores.

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

Input Schema

NameRequiredDescriptionDefault
autoNoSó o que a aprovação automática publicou.
limitNoQuantas (1 a 100; padrão 20).
offsetNoQuantas pular (0 = as mais recentes). Use o next_offset da resposta.
statusNoFiltrar por status (PENDING, APPROVED, REJECTED, DISCARDED, ...).
channelIdNoFiltrar por canal-fonte.

Output Schema

NameRequiredDescriptionDefault
historyNoOfertas capturadas, mais recentes primeiro.
successNo
has_moreNo
next_offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the read-only, non-destructive, closed-world profile, so the bar is lower. The description still adds ordering (most recent first) and the pagination contract ('com has_more true, repita com offset = next_offset'), which is real behavioral context an agent needs to page correctly.

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?

Three sentences: what is returned, why to use it, then pagination/ordering. Front-loaded and free of filler, though the before→after parenthetical is slightly dense.

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?

An output schema exists, so return values need not be explained, and the description still previews has_more/next_offset for the paging loop. For a zero-required-param read tool this is essentially complete; only fallback guidance when no filters are given 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% and every parameter (auto, limit, offset, status, channelId) is documented in the schema, so the baseline is 3. The description only reinforces offset semantics via the next_offset loop; it adds no meaning for auto, status, or channelId beyond the schema.

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 resource (últimas ofertas capturadas pelo Puxador) and enumerates what it returns: raw channel text, final text after rules/link conversion, status, destination, and decider. This makes it clearly the audit/history tool, distinguishable from list_userbot_queue (pending queue) and activity_history without opening a schema.

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 two concrete use cases: tuning a channel's rules with real examples, and diagnosing why an offer came out a certain way. Strong context, but it never names the alternative tools (list_userbot_queue, preview_userbot_rules) or states when this history is the wrong choice.

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