Radar noEixo

List enrollments

list_enrollments

Read-only

📋 CADÊNCIAS DE PROSPECÇÃO — Lista as matrículas de contatos em cadências de prospecção, paginado. Mostra status (active=ativa, paused=respondeu, completed=concluída, waiting_manual=tarefa pendente), progresso dos steps e próximo envio agendado. Pra cadências grandes (milhares de matrículas), use count_enrollments primeiro pra saber o tamanho antes de paginar tudo.

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

Input Schema

Name	Required	Description
`limit`	No	Número máximo de resultados por página (padrão: 20, máximo: 500)
`offset`	No	Quantos resultados pular — pra paginar, incremente pelo `limit` a cada chamada (padrão: 0)
`status`	No	Filtrar por status (opcional)
`replied`	No	"true" retorna só quem já respondeu algo (repliedAt preenchido); "false" só quem nunca respondeu (opcional)
`sequence_id`	No	Filtrar por cadência específica (opcional — obtido via list_sequences)
`current_step`	No	Filtrar por índice do step ATUAL (0-based) — ex: "1" pega quem já concluiu o step 0 e está esperando/prestes a receber o step 1 (opcional)
`min_steps_done`	No	Filtrar por progresso mínimo — ex: "1" retorna só quem já recebeu pelo menos 1 toque (stepsDone >= N) (opcional)
`target_user_id`	No	ID da conta-alvo (opcional; APENAS o admin da plataforma pode usar). Padrão: a conta autenticada.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the description is free to add value — and it does: pagination behavior, the shape of returned data, and a scale caveat about paginating thousands of records. It does not mention ordering guarantees or what an empty result implies, which keeps it short of a 5.

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 dense sentences with the resource definition front-loaded and the pagination warning last. The emoji/all-caps section header is mild noise but does not displace substantive content.

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 an 8-parameter, all-optional read tool with no output schema, the description covers what is listed, the paging model, and the scale escape hatch. The remaining gap — default sort order and what the pagination envelope returns — is minor since the schema documents limit/offset defaults.

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 coverage is 100%, so baseline would be 3, but the description adds meaning the schema lacks: it explains that status 'paused' actually means the contact replied and 'waiting_manual' means a pending manual task, which is non-obvious semantics an agent cannot infer from the enum alone.

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 and resource (list enrollments of contacts in prospecting cadences) plus the scope qualifier 'paginado'. It also enumerates the returned fields (status, step progress, next scheduled send), which lets an agent distinguish it from list_sequences and sequence_stats 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 one explicit routing rule: for large cadences (thousands of enrollments) call count_enrollments first to size the result before paginating. That is a real alternative-selection condition, but no guidance is given on when to prefer sequence_stats or manage_enrollment, or when the status/replied filters are the right entry point.

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

All Radar noEixo tools Inspect

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

Need Help?