Skip to main content
Glama
Sign In

Arkham

by com.arkm
OverviewDiscussionsAdmin

GetHypercoreSubAccounts

Read-onlyIdempotent

Get HyperCore sub-accounts

Sub-accounts (name, address, vault flag) indexed for a HyperCore master address.

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

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this is a read-only, idempotent, non-destructive, open-world lookup. The description adds useful context beyond annotations: the returned sub-account fields and the explicit cost of 1 API credit per call.

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?

The description is three short, front-loaded statements: purpose, returned data, and cost. Every sentence adds useful information without 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?

For a simple read-only lookup with annotations covering safety and no output schema, the description supplies the key context: input scope, returned fields, and cost. It falls short only on sibling-tool disambiguation and sub-account-specific behavior.

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?

The only input is a nested path.address. The description indicates the address should be a HyperCore master address, which adds some meaning, but it does not explain the nested path wrapper or resolve the schema note that the address may be either a master or sub-account address.

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 states a specific verb and resource: get HyperCore sub-accounts. It also lists the returned fields (name, address, vault flag) and ties the data to a HyperCore master address. It does not explicitly distinguish this from sibling tools such as GetHypercoreAccountSummary or GetHypercoreEntitySummary.

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?

The description implies the tool is used when you have a HyperCore master address and need its indexed sub-accounts. It does not state when to choose this tool over related Hypercore tools or when it should not be used.

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