Skip to main content
Glama

mcp-server

by xyz.lonestaroracle
OverviewDiscussionsAdmin

wallet_pnl

Realized/unrealized profit-and-loss and trade history for a Base wallet address over a lookback window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoLookback window in days.
walletYesBase wallet address (0x…).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / days / description
      Added value: +"Lookback window in days."
    • addedInput schema / properties / days / maximum
      Added value: +365
    • addedInput schema / properties / days / minimum
      Added value: +1
    • addedInput schema / properties / wallet / description
      Added value: +"Base wallet address (0x…)."
    • addedInput schema / properties / wallet / minLength
      Added value: +1
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are present, so the description carries the full burden of explaining behavior. It implies a read-only query through terms like 'history,' but it does not explicitly state whether the operation is read-only, what the response contains structurally, or any access requirements or limitations.

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 a single compact sentence with no filler. It front-loads the core concept and communicates the essential scope and window in a very small number of words.

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?

For a relatively simple two-parameter tool, the description captures the core functionality. However, with no annotations, no output schema, and no usage guidance, an agent is left without information about return format, read-only guarantees, or when to prefer this tool over siblings.

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%, with both 'days' and 'wallet' already explained. The description adds context about the output (PnL and trade history) but does not need to elaborate on parameter semantics because the schema already covers them.

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 names the resource (a Base wallet address), the data (realized/unrealized PnL and trade history), and the time scope (lookback window). It is clear enough to identify the tool's purpose, though it lacks an explicit verb and does not directly distinguish itself from siblings.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as smart_money or token_scan. There are no stated conditions, exclusions, or context clues beyond the inherent scope implied by 'Base wallet address.'

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

All mcp-server 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