Skip to main content
Glama

analyze hyperliquid us stock perp

analyze_hyperliquid_us_stock_perp
Read-only

Analyze U.S. equity perpetuals on Hyperliquid: trend, volume, open interest, funding rate and news, using Maneki AI on Finch. Returns the agent's official description, price, free runs, a run link and a ready-to-send request.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "analyze_hyperliquid_us_stock_perp"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoOptional short description of what the user wants. Do not include private documents or secrets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and open-world profile are covered. The description adds valuable context about what is returned (agent's official description, price, free runs, run link, ready-to-send request) and implies a cost model, which goes beyond the annotations.

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?

The description is compact and front-loaded: it starts with the analysis target, then lists the data dimensions and return items. Every clause contributes information, though the second sentence is dense and could be broken for readability.

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?

Given the open-world nature and absence of an output schema, the description is adequate but incomplete. It explains what is analyzed and what is returned, but leaves unclear how the 'ready-to-send request' should be used or what 'free runs' implies operationally.

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?

There is one optional parameter ('task') with 100% schema description coverage, so the schema fully explains it. The description adds no parameter-level detail, which is acceptable given the high coverage; baseline 3 applies.

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 and resource: 'Analyze U.S. equity perpetuals on Hyperliquid,' and enumerates the analysis dimensions (trend, volume, open interest, funding rate, news). This clearly sets it apart from sibling tools like analyze_singapore_condo or monitor_market_trading_setups, though it stops short of explicitly naming alternatives.

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

Usage Guidelines2/5

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

The description never states when to use this tool versus alternatives, nor does it include prerequisites or exclusions. The closest thing to guidance is the resource scope, but there is no explicit routing advice.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.