fluig-mcp

fluig_process_event_get

Retrieves the source code of a Fluig process event (serviceTask/beforeTaskSave) by process code, version, event name, and environment, without requiring a widget.

Instructions

Lê o código de um evento de PROCESSO (serviceTask/beforeTaskSave) via event_proces — sem widget.

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": {
      "processCode": "<processCode>",
      "eventName": "<eventName>",
      "version": "<version>",
      "env": "<env>"
    },
    "name": "fluig_process_event_get"
  }
}

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.
`version`	Yes	NUM_VERS
`eventName`	Yes	ex: servicetask71
`processCode`	Yes	trecho do COD_DEF_PROCES, ex: PROC01

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.3.0Nov 2, 2026

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"
+}

changedInput schema / properties / eventName / description

Previous value: -"Event name, e.g. \"beforeTaskSave\" or \"servicetask71\"."New value: +"ex: servicetask71"

changedInput schema / properties / processCode / description

Previous value: -"Fragment of COD_DEF_PROCES."New value: +"trecho do COD_DEF_PROCES, ex: PROC01"

changedInput schema / properties / version / description
```
Previous value: -"NUM_VERS."New value: +"NUM_VERS"
```

changedInput schema / required

Previous value: -[
-  "processCode",
-  "eventName",
-  "version"
-]New value: +[
+  "processCode",
+  "eventName",
+  "version",
+  "env"
+]

First observedv0.1.0Jul 29, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It signals a read operation ('Lê') and the underlying API ('event_proces'), but says nothing about permissions, what happens if the event is absent, or the shape/limits of the returned code.

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?

A single front-loaded sentence with no padding. It is efficient, though the terse 'sem widget' / 'via event_proces' phrasing is somewhat cryptic without further explanation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description should carry return-value and behavioral context. It conveys the tool returns event code, but leaves the 4 required parameters' operational implications and the 'sem widget' distinction unexplained.

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 coverage is 100% and each parameter (env, version, eventName, processCode) is documented in the schema, so the baseline is 3. The description adds nothing about parameter meaning beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

État a specific verb 'Lê' plus the resource 'código de um evento de PROCESSO', and narrows scope with the event types serviceTask/beforeTaskSave and the 'sem widget' qualifier. It is distinguishable from siblings like fluig_process_event_set (write) and fluig_process_events_xml, though no sibling is named explicitly.

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?

The phrase 'via event_proces — sem widget' implies this is the non-widget variant of reading a process event, hinting an alternative exists, but it never states when to prefer it over fluig_process_events_xml or fluig_process_event_set. Usage is left to inference.

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

Deploy Server