Skip to main content
Glama
Sign In

Arkham

by com.arkm
OverviewDiscussionsAdmin

GetHypercoreAccountSummary

Read-onlyIdempotent

Get HyperCore account value summary

Total account value for a HyperCore address, matching Hyperliquid's own account value: spot USD, staked HYPE and vault equity, plus perp equity where the account mode keeps perps separate from spot. A master address aggregates across all of its sub-accounts; a sub-account returns only its own value.

Costs 1 API credits per call.

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": {
      "path": "<path>"
    },
    "name": "GetHypercoreAccountSummary"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds real value beyond them: a stated cost of 1 API credit per call and the aggregation semantics (master aggregates all sub-accounts, sub-account returns only itself), which an agent cannot infer from 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 core statement is front-loaded in the title line, followed by the value composition and then the address-scoping rule, so the most decision-relevant facts come first. Slightly long at three short paragraphs, but no sentence is redundant.

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

Completeness5/5

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

With no output schema, the description compensates by enumerating the components of the returned value and stating the aggregation rule for master addresses. Cost is disclosed and the single input's dual semantics are covered, so nothing an agent needs in order to call this correctly is missing.

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?

Schema description coverage is effectively 0% at the wrapper level, so the description carries the burden and does so for the one meaningful input: it explains that an address may be either a master or a sub-account and how that changes the returned scope. It does not explain the nested 'path' wrapper structure, which is the only remaining gap.

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 gives a specific verb and resource ('Get HyperCore account value summary') and defines exactly what the value comprises: spot USD, staked HYPE, vault equity, and perp equity where kept separate. This is well beyond a tautology and it usefully separates the tool from GetHypercoreSpotBalances or GetHypercorePerpPositions, but it never names the closest sibling (GetHypercoreEntitySummary) so the boundary against that one stays implicit.

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 master-vs-sub-account note tells the agent that a sub-account address yields only its own value, which is a practical selection hint. However, there is no explicit when-to-use/when-not or named alternative, and nothing tells the agent whether to prefer this over GetHypercoreEntitySummary or the position/balance endpoints.

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

All Arkham toolsInspect
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