Skip to main content
Glama
Sign In
fluig-mcp

fluig-mcp

by alucardigo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fluig_process_version_withdraw

Withdraws a released process version from test or production to revert a bad deployment; requires confirmation and must run before deleting that released version.

Instructions

⚠️ ESCRITA. RETIRA do ar (withdraw) uma versão do processo — inverso do release. É o jeito de REVERTER um deploy ruim, e é obrigatório antes de apagar uma versão liberada. Exige confirm=true.

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

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 true
versionNoversão (opcional; omitido = latest)
processIdYesid do processo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.3.0
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true to actually perform the operation."New value: +"obrigatório true"
    • 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 / processId / description
      Previous value: -"Process id."New value: +"id do processo"
    • changedInput schema / properties / version / description
      Previous value: -"Version (optional; omitted means latest)."New value: +"versão (opcional; omitido = latest)"
    • changedInput schema / required
      Previous value: -[
-  "processId"
-]New value: +[
+  "processId",
+  "env"
+]
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it flags this as a WRITE, describes the destructive effect as taking a version offline, and mandates confirm=true. It omits permissions/auth requirements and does not say what happens to in-flight instances on that version, which keeps it short of a 5.

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 compact sentences, warning and verb front-loaded, with the prerequisite and confirmation constraint packed in without waste.

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?

No output schema and no annotations, so the description must cover behavior, and it does cover the write/offline effect, reversal intent, and deletion prerequisite. Minor gaps remain around permissions and the fate of running requests tied to the withdrawn version.

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 every parameter is already documented, including the env enum and the optional version defaulting to latest. The description only restates the confirm=true rule, adding no syntax or format detail beyond the schema, 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 specific verb and resource ('RETIRA do ar (withdraw) uma versão do processo') and immediately contrasts it with siblings: it is the inverse of fluig_process_version_release and a prerequisite for fluig_process_version_delete. An agent can distinguish it from both without opening either schema.

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?

Gives an explicit when-to-use case ('É o jeito de REVERTER um deploy ruim') and an explicit ordering constraint ('é obrigatório antes de apagar uma versão liberada'), which also routes the agent to release/delete siblings. The confirm=true precondition is stated up front.

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