Flux Cloud MCP server

Official

Overview Schema Source Related Servers Discussions Admin

Get the Flux Cloud rate card

flux_get_pricing

Fetch current USD pricing, live FLUX/USD rates, pay-in-FLUX discounts, and instant cost estimates for reference sizes; use flux_quote_app for exact app quotes.

Instructions

Returns the current USD rate card, the live FLUX/USD rate, the pay-in-FLUX discount and instant USD estimates for a few reference sizes. Use flux_quote_app for the exact price of a specific app.

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": "flux_get_pricing"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Sep 11, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations exist, so the description carries the full burden. It discloses that the returned rate is 'live' and distinguishes reference estimates from exact quotes, which is genuinely useful, but it says nothing about caching/refresh cadence, rate limits, or auth needs, and 'a few reference sizes' is vague about contents.

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?

Two sentences, zero filler. The payload of what is returned is front-loaded, and the sibling routing is placed last where it naturally reads as a caveat.

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 output schema, the description does the necessary work of enumerating the return contents, and it covers the read-only nature implicitly through 'Returns' and 'live.' It falls slightly short on the shape of the estimates (which reference sizes, refresh timing), but is otherwise complete for a no-arg read tool.

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 nothing to disambiguate and the baseline is 4. The description correctly implies no inputs are needed to obtain the rate card.

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 names a specific verb ('Returns') and enumerates the exact resources returned: the USD rate card, live FLUX/USD rate, pay-in-FLUX discount, and reference-size USD estimates. It also distinguishes itself from flux_quote_app, so an agent can tell the two apart without opening a schema.

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?

It explicitly routes the agent to flux_quote_app 'for the exact price of a specific app,' which implicitly defines when to use this tool (general rate card / rough reference estimates) versus the alternative. It stops short of an explicit when-not or a stated prerequisite, but the routing is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server