Skip to main content
Glama
Sign In
fluig-mcp

fluig-mcp

by alucardigo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fluig_globalevent_save

Create or update a global event in Fluig, explicitly choosing test or production and requiring confirmation before writing to production.

Instructions

Cria ou atualiza um evento global.

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": {
      "eventId": "<eventId>",
      "code": "<code>",
      "env": "<env>"
    },
    "name": "fluig_globalevent_save"
  }
}

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.
codeYescódigo JS
confirmNoobrigatório em env="prod" (em homologação passa direto)
eventIdYesid do evento global

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.3.0
    • changedInput schema / properties / code / description
      Previous value: -"JavaScript source."New value: +"código JS"
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "obrigatório em env=\"prod\" (em homologação passa direto)",
+  "type": "boolean"
+}
    • 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 / eventId / description
      Previous value: -"Global event id."New value: +"id do evento global"
    • changedInput schema / required
      Previous value: -[
-  "eventId",
-  "code"
-]New value: +[
+  "eventId",
+  "code",
+  "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 behavioral burden but provides almost none. It does not disclose that env="prod" is a real production write requiring confirm=true, nor anything about reversibility, overwrite semantics, or permissions — despite this being a mutation tool.

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 waste, though it is arguably too terse given the tool's production-write risk. It is efficient but leaves important context for elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter mutation tool with no annotations and no output schema, the description is incomplete. It omits the most consequential behavior — that env="prod" writes to real production and requires confirm=true — and says nothing about what an upsert returns.

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 the schema already documents env, code, confirm, and eventId thoroughly, including the production safety constraint. The description adds no parameter-level meaning beyond the schema, which is the baseline 3 under full coverage.

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?

The description names a specific verb pair ('Cria ou atualiza') and the resource ('evento global'), so an agent knows this is an upsert for global events. It does not distinguish itself from siblings like fluig_globalevent_list or fluig_globalevent_delete, but the action type makes the distinction reasonably inferable.

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 tool versus fluig_globalevent_list, fluig_globalevent_delete, or other event tools, and no mention of prerequisites. The critical production-confirmation requirement exists only in the schema, not in the description.

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