Skip to main content
Glama
Sign In
0xarchive-mcp

0xarchive-mcp

by 0xArchiveIO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

get_hip4_open_interest_current

Read-onlyIdempotent

Retrieve the current per-side open interest for a HIP-4 outcome market coin. Returns the latest open interest and implied probability.

Instructions

Get the current HIP-4 per-side open interest for a coin (e.g. '0'). Bare numeric coins are canonical; legacy '#0' / '%230' forms are also accepted.Returns the latest OI row; mark_price is an implied probability (0..1). For paired-set / display OI use get_hip4_outcome.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "coin": "<coin>"
    },
    "name": "get_hip4_open_interest_current"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinYesHIP-4 outcome-market coin symbol. Canonical form is the bare numeric '<10*outcome_id + side>' (e.g. '0' for outcome 0 Yes, '1' for outcome 0 No, '10' for outcome 1 Yes). The legacy '#0' and '%230' forms are also accepted. Use get_hip4_instruments to list all.

Output Schema

NameRequiredDescriptionDefault
dataYesResult data object

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.9.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true. Description adds beyond: explains that mark_price is implied probability (0..1), notes legacy coin forms, and that only latest row is returned.

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?

Three concise sentences. Purpose in first line, additional details in second and third, no filler words. Efficient and front-loaded.

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 output schema present, description adequately covers purpose, parameter, and key behavioral points. Could have mentioned return row fields but output schema handles that.

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 baseline is 3. Description adds example coin '0' and legacy forms '#0'/'%230', plus a reference to get_hip4_instruments for listing all coins, providing extra guidance.

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?

Clear verb 'Get' with specific resource 'current HIP-4 per-side open interest for a coin'. Example coin '0' and explicit differentiation from sibling get_hip4_outcome for paired-set/display OI.

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?

States when to use (get current per-side OI) and explicitly when not (use get_hip4_outcome for paired-set/display OI). Also explains coin format acceptance.

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