Skip to main content
Glama
parkyucheol-del

AlphaPipeline

by parkyucheol-del
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

prediction.hip4_price

Look up the closest HIP-4 strike rung for a crypto asset's price-binary market from cached data. Compare matched_strike to your target; a gap means no nearby rung.

Instructions

Cheap-tier single-rung lookup: reuses prediction.hip4_price_ladder's
cached data and returns only the one rung whose strike is closest to
the requested strike (no new upstream call). Always check
matched_strike against your requested strike - a large gap means no
rung exists near your target, not an exact match. Use
prediction.hip4_price_ladder instead if you need the whole ladder.

Args:
    underlying: Asset symbol for crypto price-binary markets (e.g. "BTC",
        "ETH", "SOL", "HYPE").
    strike: Target price level to find the closest HIP-4 rung for.

Returns:
    On success: {"success": true, "underlying", "requested_strike",
        "matched_strike", "yes_price", "expiry", ...}
    On failure: {"success": false, "error": {"type", "message"}}

Input Schema

NameRequiredDescriptionDefault
strikeYes
underlyingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A4.6/5.0
Behavior4/5

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

No annotations, so the description carries the full burden, and it does well: it discloses that no new upstream call is made (cached reuse), that only one rung is returned, that matching is nearest rather than exact, and it documents the success/failure response shapes including an error object. It does not cover auth/permission or rate-limit behavior, keeping it short of a 5.

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

Conciseness5/5

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

Front-loaded with the tool's nature and cost profile, then usage routing, then Args/Returns. Every sentence carries information an agent needs; no filler.

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?

With no output schema and no annotations, the description supplies the return field names and error shape, which is what an agent needs to interpret results. It is essentially complete for a two-parameter read tool, missing only format/unit details for the numeric strike.

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 0%, so the description must compensate. It documents both parameters, gives concrete asset examples for underlying ('BTC', 'ETH', 'SOL', 'HYPE'), and explains that strike is a target level resolved to the closest rung. The matched_strike gap warning is the key semantic addition, though it stops short of describing units or valid ranges.

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?

States a specific verb and resource (single-rung closest-strike lookup for HIP-4 price data) and explicitly positions it against the sibling prediction.hip4_price_ladder. An agent can distinguish this 'cheap-tier' cached lookup from the full-ladder tool without opening either schema.

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?

Gives an explicit alternative and the condition that selects it ('use prediction.hip4_price_ladder instead if you need the whole ladder'), plus a when-to-be-careful rule ('always check matched_strike... a large gap means no rung exists near your target, not an exact match'). Routing is unambiguous.

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

Deploy Server

Other Tools