Skip to main content
Glama
Sign In
fluig-mcp

fluig-mcp

by alucardigo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fluig_process_available_users_start

Retrieves users eligible to receive the first task when starting a Fluig process, using the process ID, initial state, and target environment.

Instructions

Usuários aptos a receber a 1ª tarefa ao INICIAR um processo (getAvailableUsersStart).

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>",
      "state": "<state>",
      "env": "<env>"
    },
    "name": "fluig_process_available_users_start"
  }
}

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.
stateYesnº do estado inicial
processIdYesCOD_DEF_PROCES
threadSequenceNothreadSequence (opcional, default 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 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"
+}
    • changedInput schema / properties / processId / description
      Previous value: -"Process id."New value: +"COD_DEF_PROCES"
    • changedInput schema / properties / state / description
      Previous value: -"Initial state number."New value: +"nº do estado inicial"
    • changedInput schema / properties / threadSequence / description
      Previous value: -"threadSequence (optional, default 0)."New value: +"threadSequence (opcional, default 0)"
    • changedInput schema / required
      Previous value: -[
-  "processId",
-  "state"
-]New value: +[
+  "processId",
+  "state",
+  "env"
+]
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. The name plus 'Usuários aptos' convey a read-only lookup, but it says nothing about authorization requirements, what the returned user records look like, or whether an empty result is possible when the state has no eligible users.

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?

A single short sentence that front-loads the resource and the qualifying condition, with zero waste. Nothing is buried or redundant.

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 four parameters (three required), no annotations, and no output schema, the definition is adequate for selecting the tool but incomplete about return shape (list of user objects? ids and names?) and failure behavior. The rich env documentation in the schema partly compensates, leaving a moderate gap.

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 env parameter is thoroughly documented with teste/prod semantics, so the baseline is 3. The description only implicitly ties 'state' and 'processId' to the first task, adding little beyond the schema itself.

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 resource and scope: users eligible to receive the first task when a process is started, and echoes the internal method name (getAvailableUsersStart). This is far more specific than a tautology, but it does not differentiate from sibling tools like fluig_process_available_users or fluig_process_possible_assignees, which an agent could easily confuse with it.

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 phrase 'ao INICIAR um processo' implies the context in which it applies, which is useful signal. However, it never says when to prefer this over fluig_process_available_users or fluig_process_possible_assignees, nor any prerequisite such as the process version needing to be released.

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