flipr-x402

flipr_opportunity

Analyze current Flipr.bet opportunity before deciding to flip. Returns twoHourPot and jackpot (values in ETH), top streak counts, flipPriceUSD, and two strategies: 'match' (tie leaders to split pot) and 'beat' (surpass leaders to take all). Each strategy shows expected cost in ETH, number of flips needed, and ROI. ROI > 1.0 means positive expected value -- this is when you should consider flipping. Pots are in ETH; flip cost is paid in USDC via x402. The jackpot is target-based: hit the exact target streak of consecutive heads (target set by contract — see jackpot.targetStreak in this response) to win 80% of the jackpot pot. Funded by a portion of flip fees. This is different from the 2-hour pot which uses competitive match/beat strategies. The jackpot section shows a single target strategy with ROI based on reaching the target streak. Call this FIRST before using flipr_flip. FREE — rate-limited only. [pricing: {"cost":"0","currency":"FREE","type":"free","network":"eip155:8453"}]

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.8/5.0

Behavior5/5

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

No annotations exist, so the description carries full burden. It discloses return values (twoHourPot, jackpot), strategy options and ROI interpretation, currency details (ETH, USDC via x402), jackpot target mechanism, and cost/pricing behavior. This exceeds a simple read-only hint and gives rich behavioral context.

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?

The description is lengthy but information-dense; every sentence contributes to understanding purpose, output, strategies, ROI, payment, and usage ordering. It could be better structured with paragraphs or bullets, but it is not bloated or repetitive.

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

Completeness5/5

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

For a zero-parameter tool with no output schema, the description thoroughly explains what the response contains, how ROI is calculated, the difference between pot types, and operational context (free, rate-limited, call-first). No significant gaps remain.

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 has zero parameters, so schema coverage is trivially 100%. The description does not need to explain parameter semantics, and the baseline of 4 applies since no parameters exist to document.

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 opens with a specific verb+resource: 'Analyze current Flipr.bet opportunity' and distinguishes itself from sibling tools by positioning as the pre-flip analysis step, explicitly referencing flipr_flip. It clearly differentiates between the 2-hour pot and jackpot mechanics.

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

Usage Guidelines5/5

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

Explicitly instructs 'Call this FIRST before using flipr_flip', giving a clear when-to-use directive. It also contrasts with the 2-hour pot and states it is free and rate-limited, providing adequate context for when this tool should be selected over alternatives.

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

All flipr-x402 tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Each tool targets a distinct aspect of the Flipr ecosystem: game info, health/status, flipping action, pot/opportunity monitoring, agent stats, referral program, and withdrawal. No two tools have overlapping purposes; even similar-sounding ones like flipr_opportunity and flipr_pot are clearly differentiated by ROI analysis.

Naming Consistency5/5

All tool names follow a consistent 'flipr_<noun>' snake_case pattern (e.g., flipr_agent_stats, flipr_flip). The naming is predictable and intuitive, making it easy for an agent to understand the hierarchy of operations.

Tool Count5/5

With 18 tools, the server covers the full scope of a betting game with referral features. Each tool serves a clear role without bloat. The count feels well-scoped for the domain, neither too sparse nor overwhelming.

Completeness4/5

The tool surface covers core gameplay (flip, health, game info), opportunity analysis (pot, opportunity, history, subscription), agent/referral management, and payout. A minor gap is the lack of a tool to retrieve an agent's own flip history beyond aggregated stats, but this does not hinder primary use cases.

Resources

Need Help?