Skip to main content
Glama
Sign In
fluig-mcp

fluig-mcp

by alucardigo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fluig_process_version_delete

Deletes a specific BPM process version in TOTVS Fluig after explicit confirmation; withdraw released versions first, and note that deleting the last version removes the entire process definition.

Instructions

⚠️ DESTRUTIVO. Apaga uma versão do processo (faça withdraw antes se estiver liberada). ATENÇÃO: apagar a ÚLTIMA versão remove a DEFINIÇÃO DO PROCESSO inteira. 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_delete"
  }
}

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.7/5.0
Behavior5/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, and it does: it flags the operation as destructive up front, discloses the catastrophic side effect of deleting the last version, and states the confirm gate. The only minor gap is that it doesn't discuss permissions or irreversibility recovery, but the primary failure modes are all disclosed.

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?

Three short clauses, destructive warning front-loaded, then precondition, then the severe consequence, then the confirm requirement. Every sentence earns its place and nothing is padded.

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?

For a destructive delete with no annotations and no output schema, the description supplies the safety posture, the prerequisite step, the escalation warning, and the confirmation requirement. An agent has everything needed to call it correctly or decide against calling it.

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 all four parameters are already documented in the schema, including env's enum semantics and that version omitted means latest. The description only restates the confirm=true requirement and adds no syntax or behavior beyond the schema; baseline 3 is appropriate.

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: 'Apaga uma versão do processo'. It also distinguishes itself from the sibling fluig_process_version_withdraw by prescribing withdraw as the prerequisite for released versions, so an agent can route correctly without opening the 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 explicit preconditions ('faça withdraw antes se estiver liberada') and an explicit execution gate ('Exige confirm=true'). It also names the when-not consequence (deleting the last version removes the whole process definition), which is exactly the kind of decision guidance an agent needs for a delete tool.

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