Skip to main content
Glama
Sign In
FLUX MCP Server

FLUX MCP Server

by tehw0lf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_timeout

Set how long the FLUX model stays idle before automatically unloading from memory to free VRAM. Use 0 to disable auto-unload and keep it resident.

Instructions

Set the auto-unload timeout for the FLUX model. The model will automatically unload after this many seconds of inactivity. Set to 0 to disable auto-unload.

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": {
      "timeout_seconds": "<timeout_seconds>"
    },
    "name": "set_timeout"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeout_secondsYesTimeout in seconds (0 to disable auto-unload)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the timeout behavior and that 0 disables auto-unload, going beyond the schema by clarifying 'inactivity.' However, it does not mention side effects, persistence, or whether it applies to the current session only, leaving some gaps.

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?

The description is two sentences, front-loaded with the action, and every sentence adds value. It is extremely concise with no wasted words.

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

Completeness4/5

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

For a simple one-parameter setter with no output schema, the description is largely complete: it covers the action, behavior, and parameter semantics. It does not explain return values or error handling, but these are reasonably implied for a setter. It could mention that unload_model is for manual unloading, but this is not essential.

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 baseline is 3. The description restates the parameter's meaning ('Set to 0 to disable auto-unload') and adds the 'inactivity' context, but this is marginal added value over the schema's 'Timeout in seconds (0 to disable auto-unload)'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: 'Set the auto-unload timeout for the FLUX model.' It uses a specific verb ('set') and resource ('auto-unload timeout'), distinguishing it from siblings like unload_model, which handles manual unloading.

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 description implies usage by explaining the behavior ('model will automatically unload after this many seconds of inactivity'), but it does not explicitly say when to use this tool over alternatives like unload_model or provide exclusion criteria. It lacks clear context for when to choose this tool.

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