Skip to main content
Glama
Sign In

Annalist

by io.github.ryanroskowski
OverviewDiscussionsAdmin

Smart-money positioning across all perps

smart_market
Read-only

Where Hyperliquid's most profitable traders are positioned across all perps: the cohort's overall net long or short, the coins it is most net long and most net short, the biggest 24-hour changes, and coins where smart money is positioned against the crowd. Cohort definition included. Aggregates only. Signed. Not investment advice. Price: $0.02 USDC per call via x402 (Base or Solana).

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": "smart_market"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds real value beyond that by disclosing the cohort definition is included, that results are aggregates only, that values are signed, and critically the per-call cost and payment rail ($0.02 USDC via x402 on Base or Solana). It also compensates for the absent output schema by naming the returned data points.

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?

Everything is front-loaded into one dense sentence that leads with the core scope and then enumerates returns; the remaining fragments (cohort definition, aggregates only, signed, price) are short and each carries information, with no filler. 'Not investment advice' is the only marginal fragment but it is legal boilerplate for a financial tool.

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?

With no output schema and no parameters, the description carries the full burden and mostly discharges it: it enumerates the returned aggregates, flags that a cohort definition is included, and discloses payment requirements. It stops short of describing return format or structure, but an agent has enough to decide and invoke correctly.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies since no parameter explanation is needed.

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 resource (smart-money positioning) and an explicit scope (across all perps), then enumerates the exact aggregates returned: net long/short, most-long and most-short coins, biggest 24h changes, and contrarian positioning. The 'across all perps' scope distinguishes it from the single-coin sibling smart_perp without the agent needing to open either schema.

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?

Usage is implied rather than stated: the broad-scan framing ('across all perps', 'Aggregates only') steers the agent away from per-coin lookups, but the description never names smart_perp as the alternative or says when the aggregate view is preferable. Adequate but no explicit when/when-not guidance.

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

All Annalist toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources