Skip to main content
Glama
Sign In

Vectorial Data Terminal: Hyperliquid, Polymarket & yield for AI agents

by com.vectorialdata
OverviewDiscussionsAdmin

unstake_hype

Unstake HYPE (free): with validator, undelegate it first (a delegation is locked 1 day); then Hyperliquid's 7-day withdrawal to spot starts. Without validator, only the withdrawal of HYPE already undelegated. Works while paused. Returns operation_id + signatures_needed[]: sign EACH step with the signer it names — 'owner' = your OWNER P-256 key over payload_b64 (decode it and check every verify line against YOUR records first), 'trading_key' = your trading key over typed_data (EIP-712) — then submit_operation within 5 minutes.

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": {
      "amount_hype": "<amount_hype>"
    },
    "name": "unstake_hype"
  }
}

Input Schema

NameRequiredDescriptionDefault
validatorNoThe validator to undelegate from; omit to only withdraw HYPE already undelegated
amount_hypeYesHYPE to unstake

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past the annotations by disclosing cost (free), timing constraints (1-day delegation lock, 7-day withdrawal to spot), that it works while trading is paused, and that it is a prepare step returning operation_id + signatures_needed[]. The prepare-only nature also reconciles destructiveHint=false with an operation that reads as state-changing.

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?

Purpose is front-loaded and the two modes follow immediately, with no filler sentences. It is dense — heavy em-dash chaining and parenthetical asides — which slightly hurts scannability, but each clause carries operational information.

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?

For a two-parameter prepare tool with no output schema, it explains the return contract (operation_id, signatures_needed), which signer signs which step (owner P-256 over payload_b64 vs trading_key EIP-712 typed_data), and the 5-minute submission deadline. Nothing needed to call and complete the flow is missing.

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 the baseline is 3, but the description adds real meaning: omitting validator restricts you to withdrawing already-undelegated HYPE, and supplying it triggers a mandatory undelegation with a 1-day lock. That is a behavioral consequence the schema description only partially conveys.

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+resource ("Unstake HYPE") and immediately disambiguates the two operating modes via the validator parameter, which separates it from stake_hype, delegate_hype and prepare_withdrawal. An agent can identify the intended operation without opening the schema.

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 explicit conditional guidance: with a validator you must undelegate first; without one, only already-undelegated HYPE can be withdrawn. It also names the required follow-up (submit_operation within 5 minutes). It does not explicitly name sibling tools like delegate_hype or prepare_withdrawal as alternatives, which keeps this just short of a 5.

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

All Vectorial Data Terminal: Hyperliquid, Polymarket & yield for AI agents toolsInspect
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