Skip to main content
Glama
Sign In
0xarchive-mcp

0xarchive-mcp

by 0xArchiveIO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

get_hip4_freshness

Read-onlyIdempotent

Check how fresh HIP-4 market data is for a coin by viewing last update timestamps and lag for orderbook, trades, open interest, and L4 data types.

Instructions

Get HIP-4 data freshness for a coin (e.g. '0') across all available data types (orderbook, trades, OI, L4). Bare numeric coins are canonical; legacy '#0' / '%230' forms are also accepted.Shows when each data type was last updated and current lag.

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_freshness"
  }
}

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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint. The description adds that the tool shows 'when each data type was last updated and current lag', which is valuable behavioral context about the output. No contradictions.

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?

Two concise sentences: first sentence states purpose and scope, second provides param format and output summary. No wasted words.

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?

For a simple tool with one parameter and an output schema, the description covers the key aspects: what it does, accepted input formats, and output content. Could optionally mention that output schema provides exact structure, but not necessary.

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 schema describes the coin parameter well (canonical form, legacy forms). The description supplements by explicitly accepting legacy '#0' and '%230' forms, adding clarity beyond the schema.

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 clearly states the tool retrieves HIP-4 data freshness for a coin across multiple data types (orderbook, trades, OI, L4). It is specifically differentiated from sibling freshness tools (e.g., get_freshness, get_hip3_freshness) by the 'HIP-4' prefix.

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

Usage Guidelines3/5

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

The description implies usage for HIP-4 outcome-market coins, but does not explicitly state when to use this tool over alternatives like get_hip3_freshness or get_freshness. No exclusion or alternative guidance is provided.

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