Skip to main content
Glama
Sign In
fluig-mcp

fluig-mcp

by alucardigo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fluig_process_search

Search Fluig processes by text and optionally restrict results to the user's favorites, with an explicit choice of test or production environment.

Instructions

Busca processos por texto (searchProcess). favorite=true retorna só os favoritos do usuário.

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

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.
contentYestexto de busca
favoriteNosó favoritos (opcional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.3.0
    • changedInput schema / properties / content / description
      Previous value: -"Search text."New value: +"texto de busca"
    • 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 / favorite / description
      Previous value: -"Favourites only (optional)."New value: +"só favoritos (opcional)"
    • changedInput schema / required
      Previous value: -[
-  "content"
-]New value: +[
+  "content",
+  "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?

No annotations were provided, meaning the description must carry the behavioral load. It only addresses a minor functional detail (favorite filtering). It does not disclose behavioral traits like query limits, supported search types (metadata vs. text), or execution timing.

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?

The description is concise, focusing on the core function (searching) and the key conditional behavior (`favorite=true`). It avoids unnecessary fluff.

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 complex system like Fluig, the description is incomplete. It does not state if the search is restricted to certain status processes, whether it searches names or descriptions, or what the search mechanism's limitations are, which is crucial context for a generic search tool.

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?

Given the schema description coverage is 100%, the baseline is 3. The description merely repeats the information already present in the input schema (e.g., 'texto de busca' for 'content'). It adds no deeper semantic meaning beyond what is structured.

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 clearly identifies the tool's function as searching for processes by text and mentions the specific effect of the 'favorite' parameter. While functional, it could better distinguish itself from other generic 'search' tools in the long list of Fluig siblings.

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 description only provides guidance on one specific parameter: setting 'favorite' to true to filter results. It fails to explain when this search tool should be used versus dedicated listing or retrieval tools, lacking explicit boundaries for its use case.

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