fluig-mcp

fluig_dataset_save

Upserts a CUSTOM Fluig dataset by ID using provided JavaScript, with explicit test or production environment selection and production confirmation.

Instructions

Cria ou atualiza (upsert) um dataset CUSTOM com o código informado.

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>",
      "code": "<code>",
      "env": "<env>"
    },
    "name": "fluig_dataset_save"
  }
}

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.
`code`	Yes	código JS (função createDataset) — ES5/Rhino
`confirm`	No	obrigatório em env="prod" (em homologação passa direto)
`datasetId`	Yes	id do dataset
`description`	No	descrição (opcional)

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv1.3.0Nov 2, 2026

changedInput schema / properties / code / description

Previous value: -"JavaScript source (a createDataset function), ES5/Rhino."New value: +"código JS (função createDataset) — ES5/Rhino"

addedInput schema / properties / confirm

Added value: +{
+  "description": "obrigatório em env=\"prod\" (em homologação passa direto)",
+  "type": "boolean"
+}

changedInput schema / properties / datasetId / description

Previous value: -"Dataset id."New value: +"id do dataset"

changedInput schema / properties / description / description

Previous value: -"Description (optional)."New value: +"descrição (opcional)"

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",
-  "code"
-]New value: +[
+  "datasetId",
+  "code",
+  "env"
+]

First observedv0.1.0Jul 29, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden, and it discloses only that the operation is an upsert — it does not say that existing dataset code is overwritten and lost, that production writes are irreversible, or that a confirmation is expected. The dangerous prod path and the confirm requirement surface only in the schema, not here.

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 and the upsert qualifier placed prominently. It is efficient, though efficiency here edges toward under-specification for a destructive, environment-sensitive write.

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?

No output schema and no annotations, on a mutating tool that can write to real production, yet the description never mentions the production hazard, the required confirm flag, or what a successful save returns. The rich env description in the schema partially compensates, keeping this from being inadequate rather than absent.

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 env/confirm/code/datasetId are already well documented; baseline 3 applies. The phrase 'com o código informado' adds little and is arguably ambiguous, since in the schema 'code' means Rhino/ES5 JavaScript while the description's 'código' reads like a dataset identifier — a distinction the agent must resolve from the schema.

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 pair and resource with the important upsert nuance spelled out ('Cria ou atualiza (upsert) um dataset CUSTOM'), so the agent knows this is idempotent-ish create-or-modify rather than pure create. It does not differentiate from close siblings such as fluig_dataset_admin, fluig_dataset_enable, or fluig_dataset_delete, so the agent must infer which dataset tool is appropriate from the names alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus fluig_dataset_admin, fluig_dataset_structure, or fluig_dataset_save's counterpart operations, and no mention of the prerequisites (the prod confirm flag) that gate a successful call. The only contextual signal is the word 'CUSTOM', which hints at scope but is never defined.

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

Deploy Server