Skip to main content
Glama

sei_listar_documentos

Read-only

List documents of a SEI process with customizable ordering and pagination. Supports ascending/descending order, offset/limit pagination, and summarized or full document details.

Instructions

Lista os documentos de um processo SEI, com ordenação e paginação.

Aceita o protocolo formatado (ex: 50300.000123/2025-00) ou o IdProcedimento.

  • ordem: 'asc' (ordem da árvore, o padrão do SEI) ou 'desc' (mais recentes primeiro). Em processo antigo e volumoso, 'desc' é como achar o documento que você acabou de criar sem varrer a lista inteira.

  • limite/offset: recorte da lista já ordenada (offset é em ITENS, não página).

  • resumido: True (padrão) devolve id, protocoloFormatado, tipo, unidade, nome, flags de assinado/cancelado e nível de acesso. False devolve o payload bruto da wssei — completo, porém grande o bastante para estourar a janela de contexto em processos com muitos documentos.

A resposta traz total (do servidor), retornados e truncado. Para ler o conteúdo de um documento, use sei_ler_documento com o id. A listagem não inclui data — ela vem de sei_consultar_documento_interno (dataElaboracao).

Nota: com SEI_WEB_SCRAPER=1 a listagem vem do scraper web e estes parâmetros de ordem/paginação não se aplicam (o scraper devolve a árvore inteira).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ordemNoasc
limiteNo
offsetNo
resumidoNo
protocolo_formatadoYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations declare readOnlyHint and openWorldHint. Description adds: read-only listing, pagination semantics, resumido flag verbosity warning, behavior change with scraper. No contradiction; adds context beyond 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?

Well-structured with bullet points, front-loaded purpose. Slightly long but each sentence adds value. The scraper note might be edge case but useful. No waste.

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 input, pagination, ordering, resumido output fields, response structure (total, retornados, truncado), date absence and alternatives, scraper edge case. With output schema present, this is fully complete.

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 description compensates fully. Explains each parameter: ordem (asc/desc, desc for recent), limite/offset (item-based pagination), resumido (fields for true vs false, context warning), protocolo_formatado (accepts protocol or IdProcedimento).

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 the tool lists documents of a SEI process with ordering and pagination. It distinguishes from sibling tools like sei_ler_documento (reading content) and sei_consultar_documento_interno (getting date). The verb 'listar' and resource 'documentos' are specific.

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?

Provides explicit when-to-use: listing documents with ordering/pagination. Gives alternatives: use sei_ler_documento for content, sei_consultar_documento_interno for date. Notes that with SEI_WEB_SCRAPER=1 the parameters don't apply. Complete guidance.

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