Skip to main content
Glama
Sign In

Kellian

by app.kellian
OverviewDiscussionsAdmin

Deprecated indexed cash-flow history; historical equity marks are unavailable

kellian_get_pnl_history
Read-onlyIdempotent

Deprecated indexed cash-flow history for a wallet. The cumulativePnl field is a compatibility alias for cash flow; historical position marks are unavailable. Values are nominal human collateral units. Do not describe this as P&L, equity or return. Cached approximately 15 minutes.

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

Input Schema

NameRequiredDescriptionDefault
addressYesWallet address.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses a ~15 minute cache (staleness risk), that values are nominal human collateral units (unit semantics), that cumulativePnl is only a compatibility alias, and that historical position marks are unavailable. These are exactly the behavioral facts an agent cannot infer from annotations or schema.

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?

Four short sentences, each carrying distinct load: deprecation status, field alias, units, semantic prohibition, and cache TTL. Front-loaded with the most decision-relevant fact (deprecated) and free of filler.

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?

The tool is trivially simple (one address parameter, output schema present), and the description covers the non-obvious risks: deprecation, cache staleness, unit interpretation, and misleading field naming. Nothing an agent needs to invoke or interpret it correctly is missing.

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 coverage is 100% and the single address parameter is fully documented with a precise EVM pattern, so the schema does the heavy lifting. The description only adds the loose framing 'for a wallet', which contributes little beyond the schema.

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 opens with a specific verb and resource ('Deprecated indexed cash-flow history for a wallet') and explicitly disclaims what the data is not (P&L, equity, return), which prevents the most likely misreading of the name. It does not name a sibling tool as the preferred alternative, so it stops short of full differentiation.

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 'Deprecated' label gives implicit when-not guidance, signalling agents to avoid building on this endpoint, and the caveats about unavailable historical marks imply its limits. However, no alternative tool is named and there is no explicit statement of when this call is still appropriate.

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

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