HYPERneobroker.com

BTC 5-minute up/down market

get_updown_markets

Read-onlyIdempotent

The flagship 5-minute BTC up/down market, running 24/7 (288 sessions a day): every 5-minute session resolves off the Hyperliquid BTC mark - YES pays $1.00 if the close is above the open, NO pays $1.00 if below, exact tie refunds. PRE-SESSION ENTRIES ONLY: buy YES or NO at a flat $0.50 per unit any time before a session starts (zero fees, true 50/50). Matched YES/NO units net off and the house takes the counterparty on the imbalance at session start; house P&L is tracked per session and cumulatively in this feed. Polymarket's own 5-min BTC market odds are shown as a 0-100 benchmark. Trade with place_prediction_order {venue:"updown", market:"next", side:"yes"|"no", shares}. Free public data, no key needed to read.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 18, 2026
RemovedSep 18, 2026

Changed1 schema field changedSep 16, 2026

removedInput schema / properties / if_none_match

Removed value: -{
-  "description": "Optional ETag from the prior response; returns not_modified when unchanged.",
-  "type": "string"
-}

Changed1 schema field changedSep 15, 2026

addedInput schema / properties / if_none_match

Added value: +{
+  "description": "Optional ETag from the prior response; returns not_modified when unchanged.",
+  "type": "string"
+}

AddedSep 13, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/non-destructive. The description adds substantial value beyond that: resolution rules, house counterparty behavior on imbalance, P&L tracking in the feed, and a Polymarket benchmark. Return format isn't described but the behavioral mechanics are unusually rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the key resource and mechanics, but dense: em-dashes, ALL-CAPS emphasis, and multiple interleaved concepts (resolution, entry rules, house P&L, benchmark, trade syntax) make it longer than necessary for a zero-param read tool.

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?

Given zero params, no output schema, and rich annotations, the description supplies the domain model an agent needs (what this market is, how it resolves, how to trade it). It's nearly complete; only return-shape/pagination for the P&L feed is unaddressed.

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?

Zero parameters, so the baseline is 4. No parameter semantics are needed and none are confused; the description instead documents the domain mechanics that parameter-less calls rely on.

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 resource: the flagship 5-minute BTC up/down market, with resolution mechanics (mark-based, YES/NO payouts, tie refund). It's clearly distinct from generic get_prediction_markets, though it doesn't explicitly name that sibling as the alternative.

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?

Gives strong operational context: pre-session entries only, buy at flat $0.50 before a session starts, and even points to the trading sibling place_prediction_order with exact arguments. Lacks explicit when-not-to-use framing versus get_prediction_markets.

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

All HYPERneobroker.com tools Inspect

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

Need Help?