Skip to main content
Glama
Cyberweasel777

botindex-mcp-server

botindex_hyperliquid_intel

Analyze Hyperliquid funding rates to predict rate persistence and identify optimal entry timing for trading decisions.

Instructions

AI-powered Hyperliquid funding rate intelligence. Rate persistence prediction, optimal entry timing. $0.05

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

With no annotations, the description carries full burden but lacks behavioral details. It mentions 'AI-powered' and '$0.05' (possibly a cost), but doesn't disclose rate limits, authentication needs, data freshness, or what 'intelligence' entails (e.g., format, confidence scores). The cost hint adds minimal value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief but could be more structured; 'Rate persistence prediction, optimal entry timing' is somewhat fragmented. It's front-loaded with core purpose, but '$0.05' at the end is ambiguous—does it indicate cost or something else? Slightly inefficient.

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

Completeness2/5

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

Given no annotations and no output schema, the description is incomplete for a tool offering 'intelligence' and predictions. It lacks details on output format, data sources, update frequency, or error handling, leaving significant gaps for an AI agent to use it effectively.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param info, which is appropriate, earning a baseline 4 for not compensating unnecessarily.

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?

The description clearly states the tool provides 'AI-powered Hyperliquid funding rate intelligence' with 'rate persistence prediction, optimal entry timing', specifying the resource (Hyperliquid funding rates) and actions (prediction, timing). It distinguishes from siblings like 'botindex_hl_funding_arb' by focusing on intelligence/prediction rather than arbitrage, though not explicitly named.

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?

No explicit guidance on when to use this tool versus alternatives is provided. The description mentions 'optimal entry timing', implying usage for trading decisions, but doesn't specify contexts, prerequisites, or exclusions compared to other botindex tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Cyberweasel777/botindex-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server