Skip to main content
Glama
Sign In
fluig-mcp

fluig-mcp

by alucardigo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fluig_form_list

Lists forms in a TOTVS Fluig environment, returning documentId, version, description, and dataset, with an optional substring filter to find specific forms.

Instructions

Lista formulários (documentId, versão, descrição, dataset). Filtro opcional.

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": {
      "env": "<env>"
    },
    "name": "fluig_form_list"
  }
}

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.
filtroNosubstring para filtrar (opcional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.3.0
    • 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"
+}
    • removedInput schema / properties / filter
      Removed value: -{
-  "description": "Substring to filter by (optional).",
-  "type": "string"
-}
    • addedInput schema / properties / filtro
      Added value: +{
+  "description": "substring para filtrar (opcional)",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[]New value: +[
+  "env"
+]
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. 'Lista' implies a read, but it says nothing about permissions, whether results are paginated, how many forms may come back, or what happens when the filter matches nothing.

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 zero filler; the returned-field list is compact. It is arguably too terse rather than bloated, which is a completeness problem, not a conciseness one.

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?

For a two-parameter read tool with fully documented schema and no output schema, listing the returned fields partially compensates for the missing output schema. However, the absence of pagination/volume expectations and of any safety or environment caveats leaves gaps that annotations would otherwise cover.

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 coverage is 100%, and the env parameter is documented in detail in the schema itself (explicit choice, no default, prod vs. homologação). The description adds nothing about filtro semantics beyond the schema's 'substring para filtrar (opcional)', so baseline 3 applies.

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?

Names a specific verb ('Lista') and resource ('formulários') and enumerates the returned fields (documentId, versão, descrição, dataset), which is more than a tautology. It does not explicitly distinguish itself from adjacent siblings such as fluig_form_fields or fluig_form_full, so it stops short of a 5.

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?

The only usage hint is 'Filtro opcional', which describes a parameter, not when to choose this tool over fluig_form_fields, fluig_form_full, or fluig_form_events. No exclusions, prerequisites, or alternative routing are stated.

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