AlphaYou: Smart Money Intel

Resolve an exchange market

resolve_hyperliquid_market

Read-only

Use to resolve Nvidia, NVDA, Bitcoin, ETH or an explicit venue symbol against Hyperliquid metadata. Returns alternatives, ambiguity and coverage. A perpetual contract is not the underlying stock.

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": {
      "asset": "<asset>"
    },
    "name": "resolve_hyperliquid_market"
  }
}

Input Schema

Name	Required	Description	Default
`asset`	Yes	Market name, like Nvidia, BTC or NVDA

Output Schema

Name	Required	Description	Default
`kind`	Yes
`status`	Yes
`requested_asset`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "kind": {
+      "const": "market_resolution",
+      "type": "string"
+    },
+    "requested_asset": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "kind",
+    "status",
+    "requested_asset"
+  ],
+  "type": "object"
+}

Changed1 schema field changedNov 12, 2026
- addedInput schema / properties / asset / description
```
Added value: +"Market name, like Nvidia, BTC or NVDA"
```
First observedOct 11, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: it returns alternatives, ambiguity and coverage, and warns that a perpetual contract is not the underlying stock — a semantic caveat an agent would otherwise get wrong.

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 short sentences, front-loaded with the use case, then the return shape, then the key caveat. 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?

Output schema exists, so return values need not be explained, and the description still names the key response fields. For a one-parameter resolution tool this is close to complete; only the absence of sibling routing keeps it from full marks.

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 coverage is 100% with a single documented 'asset' parameter, so the baseline is 3. The description broadens the expected input vocabulary (Nvidia, NVDA, Bitcoin, ETH, explicit venue symbol) which slightly exceeds the schema example, but adds no format or validation detail.

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 verb+resource: resolving an asset name (Nvidia, NVDA, Bitcoin, ETH) against Hyperliquid metadata. The closing note that a perpetual contract is not the underlying stock usefully distinguishes the resolved entity type, though it does not name a sibling tool for comparison.

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?

'Use to resolve...' implies the usage context — mapping loose asset names to venue symbols before other calls — but there is no explicit when-not guidance or named alternative among the many sibling tools. The agent must infer that this is a disambiguation step.

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

All AlphaYou: Smart Money Intel 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?