Skip to main content
Glama

sei_listar_processos

Read-only

List processes from the current unit's control box with typed fields, pagination, and server-side filtering. Retrieve only personal processes or count total items efficiently.

Instructions

Lista processos da caixa da unidade atual (Controle de Processos), em formato ENXUTO e tipado, próprio para consumo por agente.

IMPORTANTE: chame sei_trocar_unidade ANTES para que atribuido_unidade_atual seja resolvido corretamente para a unidade consultada (sem isso vem null).

Parâmetros:

  • pagina: número da página (0=primeira). Cada página tem limit itens.

  • limit: itens por página (padrão 50).

  • apenas_meus: "S" para só processos atribuídos ao usuário (server-side).

  • filtro: busca textual server-side (protocolo, tipo, especificação, etc.).

  • tipo: substring (case-insensitive) no nome do tipo processual (client-side).

  • apenas_contar: se True, retorna só {total_itens, paginas} — barato, sem baixar a página pesada.

  • incluir_detalhe: se True, reanexa ciencias e anotacoes completas a cada item (fora da list view por padrão, para manter o payload pequeno).

Cada processo (list view) traz campos derivados e tipados:

  • id_procedimento, protocolo, tipo, descricao (texto limpo, sem entidades HTML)

  • acesso: "publico" | "restrito" | "sigiloso"

  • atribuido_unidade_atual: {id_usuario, nome} resolvido para a unidade da sessão, ou null se não houver atribuição nela

  • gerado_ou_recebido, em_tramitacao, sobrestado, bloqueado, tem_documento_novo, tem_anotacao, tem_ciencia — todos BOOLEAN

  • marcador: {nome, cor} ou null · prazo: data ISO (aaaa-mm-dd) ou null

  • aberto_em_unidades: lista de siglas das unidades onde o processo está aberto

NOTA: processos sobrestados e concluídos não aparecem. Para agrupamento estatístico use sei_resumo_processos.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tipoNo
limitNo
filtroNo
paginaNo
apenas_meusNo
apenas_contarNo
incluir_detalheNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already provide readOnlyHint and openWorldHint. The description adds behavioral details: pagination behavior, filtering options, counting mode, detail inclusion, and the fact that some processes are hidden. No contradictions with annotations.

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?

The description is lengthy but well-structured: purpose first, then an important prerequisite note, then parameter details, then output format. Every sentence adds value, but could be more concise by merging some parameter descriptions.

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?

Given the tool's complexity (7 parameters, all optional, filtering, pagination, counting), the description is thorough: covers prerequisites, all parameters, output fields, and exclusions. An output schema exists, so return values are already formalized, but the description still provides useful context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the full burden. It explains every parameter in detail (pagina, limit, apenas_meus, filtro, tipo, apenas_contar, incluir_detalhe) with meanings, defaults, and effects. This adds significant value beyond the schema's bare property names.

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?

The description clearly states it lists processos from the current unit's box in a lightweight, typed format. It distinguishes itself from sibling tools like sei_pesquisar_processos (search) and sei_resumo_processos (aggregation) by mentioning its specific format and purpose.

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?

Provides explicit prerequisite (sei_trocar_unidade before using to resolve atribuido_unidade_atual) and exclusions (sobrados and concluded processes not shown). Suggests sei_resumo_processos for statistical grouping. However, it does not compare to all similar sibling tools (e.g., when to use sei_listar_processos vs sei_pesquisar_processos).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SEI-Pro/mcp-seipro'

If you have feedback or need assistance with the MCP directory API, please join our Discord server