Skip to main content
Glama

TapeOut Rigs Listed Below Fair Price

deals
Read-only

Use when you want a shortlist of TapeOut rigs to consider buying, before calling buy. TapeOut mining rigs on BNB Chain listed now below their fair price (median BNB price of recent sales of the same CPU and mining power), only where the fair price rests on at least 3 sales (raise minSales for stricter results; every item shows its sales count). Each item: price, fair, sales, hours, underFairPct and a buy link on owlgate.xyz (the buyer signs in their own wallet; OwlGate adds a 1% fee, 0.8% for subscribers; the exact fee is in the buy tx). Deepest discount first. Estimate, not advice; listings can sell at any time.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax items (default 10, max 50)
minSalesNoMinimum sales behind the fair price (default 3, lowest allowed 3)
minDiscountPctNoMinimum % below fair (default 5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / minSales / description
      Previous value: -"Minimum sales behind the fair price (default 5, lowest allowed 3)"New value: +"Minimum sales behind the fair price (default 3, lowest allowed 3)"
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare a read-only, open-world read, and the description layers on genuinely new behavior: sorting by deepest discount, the fields each item returns (price, fair, sales, hours, underFairPct, buy link), the off-site wallet-signing flow, the 1%/0.8% OwlGate fee with the exact fee only visible in the buy tx, and the risk that listings can sell at any time. This goes well past what the annotations convey.

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 trigger condition is front-loaded and every clause carries information (selection rule, result fields, fees, disclaimer). The middle section is dense with stacked parentheticals, which makes it slightly harder to scan than it needs to be, but nothing is filler.

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?

With no output schema, the description takes on return-value explanation and does so by enumerating the item fields and the ordering. Fee structure, off-platform purchase path, and the non-advice caveat cover the remaining risk surface, so an agent has everything needed to call and interpret results.

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 defaults and bounds are already documented, giving a baseline of 3. The description adds meaning beyond that by explaining that minSales controls statistical strictness of the fair-price estimate and that each result carries its sales count so the user can judge the baseline.

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 names a concrete resource (TapeOut mining rigs on BNB Chain) and a precise selection rule (listed below a fair price defined as the median of recent sales, gated at 3+ sales). It is clearly a screening/shortlist tool, explicitly positioned ahead of `buy`, so an agent can distinguish it from the purchase sibling without inspecting schemas.

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?

Explicit trigger: 'Use when you want a shortlist of TapeOut rigs to consider buying, before calling buy,' which also establishes the ordering relationship with `buy`. It adds a tuning hint ('raise minSales for stricter results') but gives no exclusion such as when to skip this tool and query a specific rig or fair price directly.

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