Skip to main content
Glama

Ask flux

ask_flux

Ask Flux (ERC-8004 passport #1 on Arc) a question ($0.02); response recorded on G2. $0.02 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": {
      "q": "<q>"
    },
    "name": "ask_flux"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesyour question for Flux (at least 4 characters)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 and does reasonably well: it discloses cost ($0.02 per call), accepted payment assets and chains (USDC on Arc/Base/Solana, XNT on X1), the two-phase x402 handshake, and that responses are recorded on G2. It omits failure semantics, e.g. whether a declined or errored call is still charged, and whether the signed payload expires.

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?

Dense and front-loaded: price, identity, and payment flow appear in the first sentences with no filler. The chain/asset enumeration is the only slightly bulky segment, though it is load-bearing for a payment tool.

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

Completeness3/5

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

Given no output schema and no annotations, the description should cover what comes back; instead it only says the response is 'recorded on G2', leaving the actual answer shape and the G2 reference unexplained. The payment mechanics are well covered, but return-value and error behavior are not.

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?

Schema coverage is 100%, so the baseline is 3; the description earns above baseline by explaining the temporal relationship between the two parameters: `payment` must be obtained after a payment-free terms call and is the signed payload that completes the purchase inside the call. That is meaning the schema alone does not convey.

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 states a specific verb and resource ('Ask Flux ... a question') and adds distinguishing identity ('ERC-8004 passport #1 on Arc') plus a price point. It is clear what happens, but it never names or contrasts against the closest sibling (ask_apex), so differentiation is left to the agent.

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 gives an explicit operational sequence: call once without `payment` to obtain terms, sign with your own wallet, call again with `payment`. That is a clear when/how-to-use instruction. It stops short of saying when this tool is preferred over similar asking tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources