fluig-mcp

fluig_process_export_xml

Downloads the XML definition of a Fluig process (.ecm30.xml), including activities, transitions, fields, and event code, to support editing the process by code.

Instructions

Baixa o XML da definição de um processo (.ecm30.xml) pela REST v2. Contém TUDO: atividades (ProcessState), transições (ProcessLink), campos e o CÓDIGO dos eventos de processo (WorkflowProcessEvent/eventDescription). Base para editar processo por código.

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": {
      "processId": "<processId>",
      "env": "<env>"
    },
    "name": "fluig_process_export_xml"
  }
}

Input Schema

Name	Required	Description
`env`	Yes	OBRIGATÓ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.
`destino`	No	arquivo para gravar o conteúdo inteiro (opcional; a resposta traz só o resumo), dentro de FLUIG_SAIDA_DIR (padrão: ~/fluig-mcp-saida); caminho relativo é relativo a ela, e caminho fora dela é recusado
`version`	No	versão específica (opcional; padrão = versão corrente)
`maxChars`	No	máximo de caracteres na resposta inline (opcional; padrão 20000)
`processId`	Yes	id do processo (ex: Suporte_TI)

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv1.3.0Nov 2, 2026

addedInput schema / properties / destino

Added value: +{
+  "description": "arquivo para gravar o conteúdo inteiro (opcional; a resposta traz só o resumo), dentro de FLUIG_SAIDA_DIR (padrão: ~/fluig-mcp-saida); caminho relativo é relativo a ela, e caminho fora dela é recusado",
+  "type": "string"
+}

addedInput schema / properties / env

Added value: +{
+  "description": "OBRIGATÓ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.",
+  "enum": [
+    "teste",
+    "prod"
+  ],
+  "type": "string"
+}

addedInput schema / properties / maxChars

Added value: +{
+  "description": "máximo de caracteres na resposta inline (opcional; padrão 20000)",
+  "type": "number"
+}

changedInput schema / properties / processId / description

Previous value: -"Process id."New value: +"id do processo (ex: Suporte_TI)"

changedInput schema / properties / version / description

Previous value: -"Specific version (optional; defaults to the current one)."New value: +"versão específica (opcional; padrão = versão corrente)"

changedInput schema / required

Previous value: -[
-  "processId"
-]New value: +[
+  "processId",
+  "env"
+]

First observedv0.1.0Jul 29, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose that the payload is the complete definition including event source code, which is genuinely useful. However, it does not state that the operation is read-only, that the inline response is truncated (maxChars) with the full content only via 'destino', or that writing a file is a side effect — those facts live only 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?

Two sentences, front-loaded with the retrieval action, then the content inventory and intended downstream use. No filler or repetition of the tool name.

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 a 5-parameter export tool with no annotations and no output schema, the definition conveys what comes back (full .ecm30.xml) and why. It stops short of describing the truncation/file-output behavior and safety profile, which the agent must infer from the schema alone.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already explains env, destino, version, maxChars and processId in detail. The description adds no parameter-level semantics of its own (it never mentions version selection or the file-output path), so the baseline 3 applies.

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 concrete verb and resource ('Baixa o XML da definição de um processo (.ecm30.xml)') plus the transport ('pela REST v2'). The enumeration of contents (ProcessState, ProcessLink, fields, event code) implicitly separates it from narrower siblings such as fluig_process_events_xml or fluig_process_states.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Base para editar processo por código' hints at the intended workflow, but there is no explicit when-to-use/when-not guidance and no named alternative (e.g. use fluig_process_events_xml for events only, or fluig_process_import_xml to write the XML back). Usage must be inferred.

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

Deploy Server