Skip to main content
Glama
Sign In

Arkham

by com.arkm
OverviewDiscussionsAdmin

GetHypercorePortfolioHistory

Read-onlyIdempotent

Get HyperCore account value / PnL history

Live account-value and PnL time series per timeframe (day, week, month, allTime) for a HyperCore address. Not aggregated across sub-accounts.

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

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world, so the description adds genuine value by disclosing the billing cost (1 API credit per call) and the sub-account aggregation scope. It stops short of describing response shape, timeframe resolution, or whether data is live vs delayed beyond the word 'Live'.

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?

Three tight lines, front-loaded with the capability and followed by scope and cost. The first line is close to a restatement of the title, so it is not perfectly waste-free, but nothing else is padded.

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?

There is no output schema, so the description carries the return-value burden; 'account-value and PnL time series per timeframe' gives the shape but no granularity, timestamp unit, pagination, or history depth. The undocumented timeframe selection and nested `path` wrapper leave the agent guessing how to actually call it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% at the top level and the only param is a nested `path.address` object that the description never explains. Worse, the description advertises 'per timeframe (day, week, month, allTime)' but the schema exposes no timeframe parameter, so the text implies an input that cannot be supplied — actively misleading about how to control the output.

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?

Specific verb+resource: 'account value / PnL history ... for a HyperCore address', with the explicit scope qualifier 'Not aggregated across sub-accounts' that separates it from the entity-level variants in the sibling list. It never names a sibling outright, so differentiation is inferred rather than stated.

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 'not aggregated across sub-accounts' note implies when to prefer GetHypercoreEntityPortfolioHistory, and the credit cost implies a budgeting consideration, but there is no explicit 'use this when / use X instead' routing and no prerequisites (e.g., valid address format) stated.

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