Skip to main content
Glama
Sign In
fluig-mcp

fluig-mcp

by alucardigo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fluig_dataset_delete

Deletes a custom Fluig dataset by ID in the chosen test or production environment, requiring confirm=true. Use it to clean up disposable ds_claude_* datasets created by the MCP.

Instructions

⚠️ ESCRITA/DESTRUTIVO. Apaga um dataset CUSTOM do servidor (ECMDatasetService.deleteDataset). Serve para o MCP limpar os datasets descartáveis que ele mesmo cria (ds_claude_*). 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": {
      "datasetId": "<datasetId>",
      "env": "<env>"
    },
    "name": "fluig_dataset_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
datasetIdYesid do dataset a apagar

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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"
    • changedInput schema / properties / datasetId / description
      Previous value: -"Dataset id to delete."New value: +"id do dataset a apagar"
    • 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 / required
      Previous value: -[
-  "datasetId",
-  "confirm"
-]New value: +[
+  "datasetId",
+  "env"
+]
  2. First observedv0.1.0

TDQS

A4.2/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 so well: a leading ESCRITA/DESTRUTIVO warning, the destructive nature of the call, the confirm gate, and the CUSTOM-dataset restriction. It stops short of stating irreversibility or whether a restore path exists (a fluig_dataset_restore sibling exists but is never referenced), which would be valuable for a delete tool.

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 sentences, with the destructive warning and the write/destructive classification front-loaded before the purpose and prerequisite. No filler; every clause adds either safety, scope or usage information.

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 3-parameter destructive tool with no annotations and no output schema, the description covers safety, scope and the confirm prerequisite, while the schema covers env semantics. The gap is the absence of post-deletion behavior (recoverability, error on non-custom datasets), which an agent would want before invoking an irreversible operation.

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 (teste vs prod), confirm and datasetId in detail, so the baseline is 3. The description only restates "Exige confirm=true"; its one genuine addition is narrowing datasetId semantics to CUSTOM ds_claude_* datasets.

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 um dataset CUSTOM do servidor") and even cites the underlying service method (ECMDatasetService.deleteDataset). The CUSTOM-only qualifier cleanly separates it from sibling mutation tools such as fluig_dataset_save, fluig_dataset_restore and fluig_dataset_admin.

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?

Explicitly frames the intended use case: cleaning up throwaway datasets the MCP itself created (ds_claude_*), which tells the agent when to reach for it rather than the other dataset tools. It also states the confirm=true prerequisite. It does not spell out a when-not-to-use case (e.g. non-custom or in-use datasets), so it stops short of a 5.

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