Skip to main content
Glama
Sign In

Radar noEixo

by com.noeixodigital
OverviewDiscussionsAdmin

Manage enrollment

manage_enrollment
Destructive

📋 CADÊNCIAS DE PROSPECÇÃO — Gerencia matrícula(s) de contato em cadência. Ações disponíveis: pause (pausa), resume (retoma), cancel (cancela), advance (executa step atual imediatamente, sem esperar o delay), repeat (re-executa o step anterior), restart (reinicia do step 0), done_manual (marca tarefa LinkedIn/Facebook como feita e avança). MODO INDIVIDUAL: informe enrollment_id (obtido via list_enrollments). MODO EM LOTE: informe enrollment_ids (vários IDs separados por vírgula) OU sequence_id (+ opcionalmente status/current_step/min_steps_done como filtro do alvo, mesmo formato de list_enrollments) — aplica a ação em todas as matrículas que baterem com o filtro, até 2000 por chamada; matrículas que não estejam no estado certo pra ação (ex: pause numa já pausada) são só puladas, não travam o lote inteiro. Use count_enrollments antes pra saber quantas seriam afetadas.

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": {
      "action": "<action>"
    },
    "name": "manage_enrollment"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYespause | resume | cancel | advance | repeat | restart | done_manual
statusNoModo em lote (com sequence_id): filtra por status antes de aplicar a ação
sequence_idNoModo em lote: aplica a ação em todas as matrículas dessa cadência que baterem com status/current_step/min_steps_done (obtido via list_sequences)
current_stepNoModo em lote (com sequence_id): filtra por índice do step atual (0-based)
enrollment_idNoModo individual: ID de UMA matrícula (obtido via list_enrollments)
enrollment_idsNoModo em lote: vários IDs de matrícula separados por vírgula
min_steps_doneNoModo em lote (com sequence_id): filtra por progresso mínimo (stepsDone >= N)
target_user_idNoID da conta-alvo (opcional; APENAS o admin da plataforma pode usar). Padrão: a conta autenticada.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare destructive=true and readOnly=false; the description goes well beyond them by explaining what each action does behaviorally (advance runs the current step immediately without the delay, repeat re-runs the prior step, restart goes back to step 0, done_manual marks a LinkedIn/Facebook task complete and advances), plus the 2000-recipient cap and that mismatched-state enrollments are skipped rather than erroring.

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?

Front-loads purpose, then action glossary, then mode routing, then the batch-limit caveat — a sensible order. It is long and the emoji header is decorative, but nearly every clause carries operational information, so the density is justified.

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 8-parameter destructive mutation tool with no output schema, the description covers action semantics, mode selection, batch size limits, failure tolerance, and the recommended preview call — everything needed to invoke it without surprises.

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 description coverage is 100%, so baseline is 3. The description adds real value on top of the schema by pairing params into modes (enrollment_id singular vs enrollment_ids/sequence_id batch) and explaining that status/current_step/min_steps_done act as target filters mirroring list_enrollments; it does not restate the admin-only nature of target_user_id, which the schema already covers.

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 (contact enrollments in a cadence) and enumerates seven distinct actions, distinguishing the tool from siblings like list_enrollments and count_enrollments. An agent immediately knows this mutates enrollment state rather than reading it.

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?

Explicitly separates individual mode (enrollment_id) from batch mode (enrollment_ids or sequence_id + filters), names the sibling tools for obtaining IDs (list_enrollments) and for previewing impact (count_enrollments), and states the skip-on-wrong-state rule so a batch won't fail. That is when-to-use, prerequisites, and alternatives in one place.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Radar noEixo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources