fluig-mcp

fluig_dataset_get

Retrieve the source code of a custom Fluig dataset from test or production, with optional file output when the full content exceeds the inline response limit.

Instructions

Retorna o código-fonte de um dataset CUSTOM (loadDataset).

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

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.
`destino`	No	arquivo para gravar o conteúdo inteiro (opcional; a resposta traz só o resumo), dentro de FLUIG_SAIDA_DIR (padrão: ~/fluig-mcp-saida); caminho relativo é relativo a ela, e caminho fora dela é recusado
`maxChars`	No	máximo de caracteres na resposta inline (opcional; padrão 20000)
`datasetId`	Yes	id do dataset custom

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.3.0Nov 2, 2026

changedInput schema / properties / datasetId / description

Previous value: -"Id of the custom dataset."New value: +"id do dataset custom"

addedInput schema / properties / destino

Added value: +{
+  "description": "arquivo para gravar o conteúdo inteiro (opcional; a resposta traz só o resumo), dentro de FLUIG_SAIDA_DIR (padrão: ~/fluig-mcp-saida); caminho relativo é relativo a ela, e caminho fora dela é recusado",
+  "type": "string"
+}

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

addedInput schema / properties / maxChars

Added value: +{
+  "description": "máximo de caracteres na resposta inline (opcional; padrão 20000)",
+  "type": "number"
+}

changedInput schema / required

Previous value: -[
-  "datasetId"
-]New value: +[
+  "datasetId",
+  "env"
+]

First observedv0.1.0Jul 29, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations exist, so the description carries the full burden. 'Retorna' implies a read-only operation and 'CUSTOM' implies internal/build datasets are out of scope, but it says nothing about permissions, whether prod access behaves the same as teste, or that the response is truncated to maxChars unless destino is used (that detail lives only in the schema).

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. It is arguably too terse for the tool's behavioral surface, but nothing in the text is wasted.

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?

With 4 parameters, no annotations and no output schema, the description leaves gaps: the shape of the returned source (inline summary vs. full file when destino is set), read-only nature, and prod safety posture are not stated. The rich schema compensates for parameter details but not for the behavioral contract.

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, destino, maxChars and datasetId are already fully documented, including the required env choice and safe output directory behavior. The description adds no parameter-level information beyond 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+resource ('Retorna o código-fonte de um dataset') and narrows the scope to CUSTOM datasets (loadDataset), which implicitly separates it from fluig_dataset_list and fluig_dataset_run. Sibling differentiation is only implied via the 'CUSTOM' qualifier, not spelled out.

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

Usage Guidelines3/5

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

The 'CUSTOM (loadDataset)' qualifier hints at when the tool applies, but there is no explicit when-to-use/when-not guidance, no pointer to fluig_dataset_list for discovering datasetId, and no mention of when to read source vs. run the dataset.

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

Deploy Server