Skip to main content
Glama
Sign In
alucardigo

fluig-mcp

by alucardigo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fluig_workflow_exporter

Exports a complete process-instance dossier with history, form data, and attachments to ZIP or text, requiring explicit environment and form-anonymization settings.

Instructions

DOSSIÊ completo de uma solicitação num artefato só (histórico, formulário, anexos). ⚠️ anonymizeForms é OBRIGATÓRIO aqui: o default do servidor é TRUE e anonimiza os formulários em silêncio — você procuraria o dado achando que sumiu. Informe destino para baixar o ZIP.

Input Schema

NameRequiredDescriptionDefault
envYesOBRIGATÓRIO. Ambiente alvo: "teste" (homologação, o host de FLUIG_HOST) ou "prod" (PRODUÇÃO REAL, o host de FLUIG_HOST_PROD). Não há default: a escolha é sempre explícita, para que ninguém leia homologação achando que é produção nem escreva em produção achando que é teste.
destinoNoarquivo .zip a gravar (opcional; sem isso devolve o dossiê em texto), dentro de FLUIG_SAIDA_DIR (padrão: ~/fluig-mcp-saida); caminho relativo é relativo a ela, e caminho fora dela é recusado
anonymizeFormsYestrue anonimiza os formulários; escolha explícita
processInstanceIdYesid da solicitação

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

A5/5.0
Behavior5/5

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

Since there are no annotations, the description bears the full burden. The alert (⚠️) explicitly reveals a major behavioral risk—the server's default state silently anonymizing data—a critical piece of context not present in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is highly efficient, front-loading the core functionality and the primary behavioral warning in a brief, impactful text.

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 lack of an output schema or annotations, the description is highly complete. It identifies the necessary steps (including setting `anonymizeForms`) to ensure a functional and non-surprising experience for the agent.

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?

The description adds critical semantic value regarding the `anonymizeForms` parameter by declaring it 'OBRIGATÓRIO' and explaining the functional consequence of relying on the server's default setting.

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 defines the tool's function as creating a 'complete dossier' (Dossiê completo) comprising the history, form, and attachments of a request. This distinguishes it as a comprehensive export utility.

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?

It provides critical operational guidance by stating that `anonymizeForms` is mandatory due to server defaults, warning the agent about the consequence of silence (losing data by mistake).

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

Deploy Server

Other Tools