Skip to main content
Glama
Sign In
@runapi.ai/flux-2-mcp

@runapi.ai/flux-2-mcp

Official
by runapi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

check_pricing

Look up RunAPI pricing for the Flux-2 model line. Compare costs by model and endpoint before creating image tasks.

Instructions

Look up RunAPI pricing for the flux-2 model line.

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

Input Schema

NameRequiredDescriptionDefault
modelNoModel slug. Defaults to the line's primary model.
actionNoEndpoint name. Defaults to the endpoint that offers the model.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / model / enum
      Removed value: -[
-  "flux-2-flex-remix-image",
-  "flux-2-max-remix-image",
-  "flux-2-pro-remix-image",
-  "flux-2-flex-text-to-image",
-  "flux-2-max-text-to-image",
-  "flux-2-pro-text-to-image"
-]
  2. Changed1 schema field changedv0.2.1
    • changedInput schema / properties / model / enum
      Previous value: -[
-  "flux-2-flex-remix-image",
-  "flux-2-pro-remix-image",
-  "flux-2-flex-text-to-image",
-  "flux-2-pro-text-to-image"
-]New value: +[
+  "flux-2-flex-remix-image",
+  "flux-2-max-remix-image",
+  "flux-2-pro-remix-image",
+  "flux-2-flex-text-to-image",
+  "flux-2-max-text-to-image",
+  "flux-2-pro-text-to-image"
+]
  3. 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 are provided, so the description carries the full burden of behavioral disclosure. It never states that this is a read-only, side-effect-free operation, nor does it mention pricing units, currency, caching, or any rate limits — a single sentence leaves most behavior opaque.

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 filler, so it is efficient and easy to parse. It is arguably under-specified rather than genuinely concise, which keeps it short of a 5.

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?

With no output schema, no annotations, and two optional parameters, the description should explain what the pricing response contains (units, currency, per-endpoint breakdown) and how the defaults resolve. None of that is present, leaving the agent guessing about the return shape.

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%, and the schema itself explains that 'model' defaults to the line's primary model and 'action' defaults to the endpoint offering the model, so baseline 3 applies. The description adds nothing about either parameter beyond what the schema already documents.

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?

States a specific verb ('look up') and resource ('pricing') scoped to the flux-2 model line, so the intent is unambiguous. However it gives no differentiation from siblings like remix_image or text_to_image, nor does it clarify whether the hardcoded 'flux-2' scope is literal or an example.

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 call this versus alternatives, no prerequisites, and no indication of whether it should be called before invoking remix_image/text_to_image. Usage can only be inferred from the tool name itself.

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