Skip to main content
Glama
Sign In

Flux Cloud

by io.github.RunOnFlux
OverviewDiscussionsAdmin

List apps owned by the configured Flux ID

flux_list_my_apps
Read-only

Lists every app registered by the owner (or a given Flux ID) with expiry and instance counts.

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_list_my_apps"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerNoFlux ID to list; defaults to the configured one.
nameContainsNoOnly apps whose name contains this text.
fluxIdPrivateKeyNoWIF private key of the Flux ID that owns the app. Use a dedicated key from flux_generate_keys, never a main wallet key.
paymentPrivateKeyNoWIF private key of the Flux address that pays. Fund it with only what you intend to spend.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that results carry expiry and instance counts, which is useful return-shape context in the absence of an output schema, but it says nothing about why a read-only list tool requires two private keys or how they are handled.

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, and the scope qualifier appears before the trailing detail about returned fields. It is tight and earns its place, though the trailing clause makes it slightly less scannable than a pure verb-resource statement.

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 read-only list tool with 100% schema coverage and no output schema, the description supplies the one thing the schema does not: what each listed app row contains (expiry and instance counts). The remaining gap is the unexplained presence of credential parameters on a read operation.

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 schema already documents all four parameters in detail. The description only restates the owner default ('or a given Flux ID') and omits nameContains and the two key parameters entirely, adding no meaning beyond the schema — baseline 3 is appropriate.

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 (Lists) and resource (every app registered by the owner), with the scope qualifier 'every app' making it distinguishable from the single-app sibling flux_get_app. It stops short of naming a sibling explicitly, so it earns a 4 rather than a 5.

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?

Usage is implied by the verb and the owner/Flux ID qualifier, but there is no explicit when-to-use statement, no mention of when to prefer flux_get_app or flux_get_app_stats instead, and no note on prerequisites for the two private-key parameters.

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

All Flux Cloud toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources