Skip to main content
Glama
Sign In

Femtos

by xyz.femtos
OverviewDiscussionsAdmin

A HyperCore wallet's PnL curve

get_hypercore_wallet_pnl
Read-onlyIdempotent

The HyperCore PnL curve of any address (or a named wallet's handle): per hour or day, realized PnL, fees, funding, net and cumulative net, plus the perp account value at each bucket's end and the net transfers in it, over 7d, 30d, 90d or all history. Account values are walked back from our node's state now (standard accounts; unified and portfolio-margin ones get none, accountValue.status says why). Open positions now: get_hypercore_account.

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": {
      "address": "<address>"
    },
    "name": "get_hypercore_wallet_pnl"
  }
}

Input Schema

NameRequiredDescriptionDefault
bucketNoBucket: 1h (window 7d or 30d) or 1d. Default 1d (default 1d)
windowNoUTC days ending today: 7d, 30d, 90d, or all (since `dataStart`). Default 30d (default 30d)
addressYes0x address, or a named wallet's handle <entityId>.<hex>

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare read-only and idempotent, but the description adds real behavior beyond them: account values are walked back from the node's current state, only standard accounts are supported, and unified/portfolio-margin accounts get none with accountValue.status explaining why. That kind of coverage caveat is exactly what an agent needs before calling.

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?

Front-loaded with purpose and granularity, then the metric list, then the account-type caveat, then the sibling pointer. It is dense but nearly every clause carries information; the field enumeration is long but earns its place since there is no output schema.

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, the description does the work of describing the return shape: realized PnL, fees, funding, net, cumulative net, perp account value and net transfers per bucket. Combined with the account-type limitation, an agent has enough to call and interpret it correctly; only rate limits or response-size expectations are absent.

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?

Schema description coverage is 100% and both enums carry their allowed values and defaults, so the description mostly restates them ('per hour or day', the window list). It adds only a light gloss on the address parameter accepting a named wallet handle, which the schema already documents.

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 verb+resource ('The HyperCore PnL curve of any address'), names the granularity (per hour or day) and the exact metrics returned. It also distinguishes itself from get_hypercore_account by assigning that tool to 'open positions now'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit routing rule at the end: use get_hypercore_account for current open positions rather than this tool. It does not, however, say when to prefer this over similar siblings such as get_wallet_pnl or get_entity_pnl, or how to pick bucket/window beyond the schema defaults.

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

All Femtos 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