Skip to main content
Glama
Sign In
fluig-mcp

fluig-mcp

by alucardigo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fluig_process_take

Claims a pooled or role-based BPM task on a Fluig process instance so it can be moved; requires explicit test or production environment and production confirmation.

Instructions

Assume/toma a tarefa (takeProcessTask) — necessário p/ tarefas de POOL/papel antes de mover.

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": {
      "processInstanceId": "<processInstanceId>",
      "env": "<env>"
    },
    "name": "fluig_process_take"
  }
}

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.
confirmNoobrigatório em env="prod" (em homologação passa direto)
processInstanceIdYesiProcess

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.3.0
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "obrigatório em env=\"prod\" (em homologação passa direto)",
+  "type": "boolean"
+}
    • 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 / processInstanceId / description
      Previous value: -"Instance number."New value: +"iProcess"
    • changedInput schema / required
      Previous value: -[
-  "processInstanceId"
-]New value: +[
+  "processInstanceId",
+  "env"
+]
  2. First observedv0.1.0

TDQS

B3.3/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 behavioral burden. It implies a mutating assignment change but says nothing about permissions needed, what happens if the task is already taken (conflict/error), whether the operation is reversible, or what is returned.

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 filler; the operational constraint is placed immediately after the verb. The telegraphic Portuguese abbreviations ('p/', 'tarefas de POOL/papel') slightly reduce readability for a non-Portuguese-speaking agent.

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

Completeness2/5

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

This is a mutation tool with no annotations and no output schema, yet the description omits failure modes (task already assigned, insufficient role), success semantics, and sequencing with the move tool. The detailed input schema compensates for call arguments but not for behavioral understanding.

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%, and the schema already explains env, the prod-only confirm requirement, and processInstanceId. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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?

States a specific verb and resource ('Assume/toma a tarefa' / takeProcessTask) and adds the essential qualifier that it applies to POOL/role tasks before moving. An agent can tell what it does without opening the schema, though the sibling it pairs with (fluig_process_move) is only implied.

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?

'necessário p/ tarefas de POOL/papel antes de mover' gives a concrete when-to-use condition and implicitly identifies the follow-up operation. It does not name the specific sibling alternatives (e.g. fluig_process_move, fluig_process_move_rest) or say when it should be skipped.

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