Skip to main content
Glama
Flux MCP

Flux MCP

Official
by Flux-Search

account

Read-only

Check your Flux balance and estimate how many Lineage input tokens it covers before running a large job.

Instructions

Show the Flux account balance, and roughly how many tokens of Lineage input it covers. Free. Check it before a large job.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "account"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds value beyond that by disclosing cost behavior ('Free') and by hedging the token figure as 'roughly', which sets correct expectations about precision. It does not describe the response shape, but the safety and cost profile an agent needs before calling is present.

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?

Three short sentences, each carrying distinct information: what is returned, that it costs nothing, and when to call it. The primary output is front-loaded and there is no filler.

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?

With no parameters and no output schema, the description must carry the burden of explaining the return value, and it does so reasonably by naming both figures returned. It could say more about units or what the balance represents, but for a zero-arg read tool this is close to complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to explain; the baseline for a no-param tool applies. Nothing in the description conflicts with the empty schema.

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 and resource: 'Show the Flux account balance,' plus a secondary output — roughly how many Lineage input tokens the balance covers. That is concrete enough to distinguish it from generic siblings like 'fetch' or 'search'. It stops short of explicitly naming which sibling to use instead, but the resource is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Check it before a large job' gives an explicit trigger condition for calling the tool, which is more than most definitions offer. It does not state when not to call it or name an alternative, but for a zero-parameter informational tool the single precondition is adequate guidance.

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