Vino & Views

hyperliquid_watch

Read-onlyIdempotent

Free. On-demand public Hyperliquid perp market snapshot with caller-selected funding and 24h price-move thresholds. No trading or scheduled push alerts.

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": {
      "request": "<request>"
    },
    "name": "hyperliquid_watch"
  }
}

Input Schema

Name	Required	Description	Default
`request`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld. The description adds genuinely new behavioral scope: the call is free, hits public data, is single-shot rather than pushed, and performs no trading. It stops short of explaining what happens when a threshold is not crossed or what the snapshot body contains.

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?

Two tight sentences with the most decision-relevant qualifier ('Free') front-loaded and the exclusion clause last. No filler, though 'Free.' as a standalone fragment is slightly promotional rather than descriptive.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with no output schema and full annotation coverage, the description covers selection but not the result. An agent cannot tell whether the response is raw market data, a threshold-crossing verdict, or both, which is the main remaining unknown before calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It does add meaning by framing the two numeric parameters as caller-selected 'funding' and '24h price-move' thresholds, but it omits units, defaults, and whether thresholds filter the response or merely annotate it; the nested 'request' wrapper and coin identifier are not addressed at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and operation: an 'on-demand public Hyperliquid perp market snapshot.' The 'free' and 'public' qualifiers plus the negative scope ('No trading or scheduled push alerts') make the tool's identity clear, though no sibling tool is named or explicitly ruled out.

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?

'On-demand' and 'No scheduled push alerts' imply a pull-based, single-shot usage pattern and exclude a subscription mode. However, the description never states a positive when-to-use condition, nor does it point to any alternative among the many sibling tools for market or risk questions.

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

All Vino & Views tools Inspect

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

Need Help?