Skip to main content
Glama
Sign In

AIDEN

by network.aiden
OverviewDiscussionsAdmin

Get agent trading record

get_agent_trading_record
Read-onlyIdempotent

An agent's public trading record on Arcus, the perpetuals and Stock Token exchange on Robinhood Chain: all-time and 30-day volume, realized PnL, fees and volume rank, plus open positions. Checks the agent wallet and the owner wallet. This is trading evidence only; it does not change the AIDEN trust score.

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": {
      "agent_id": "<agent_id>"
    },
    "name": "get_agent_trading_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesERC-8004 agent ID (token ID in the Identity Registry)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds real value beyond those flags: it states that both the agent wallet and the owner wallet are checked, and clarifies the side-effect boundary ('trading evidence only; does not change the trust score'). That is useful behavioral context, though no return format or rate-limit detail is given.

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?

One dense sentence describes the resource and its fields, followed by a short scoping clause; the purpose is front-loaded and nothing is wasted. It is borderline long, which keeps it from a 5.

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 carries the burden of describing returns — and it does so concretely (volume windows, PnL, fees, rank, open positions). Combined with the annotation coverage of safety semantics, an agent has enough to call it correctly, though wallet-address handling and result shape remain unstated.

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 a single well-documented parameter (agent_id as an ERC-8004 identity token ID). The description adds no syntax or format detail beyond the schema, so the baseline 3 is appropriate.

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 a specific verb (get) and resource (an agent's public trading record on Arcus), then enumerates the exact data returned: all-time/30-day volume, realized PnL, fees, volume rank, and open positions. It differentiates from identity/trust siblings by explicitly scoping this as 'trading evidence only.' It stops short of naming sibling tools directly, so 4 rather than 5.

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 closing clause ('does not change the AIDEN trust score') implies this is for informational/trading reads rather than trust mutation, but there is no explicit when-to-use or when-not-to-use guidance relative to get_agent, get_agent_feedback, or get_agent_validations. Usage is inferred, not stated.

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

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