sa-ecosystem-node

Player legacy

player_legacy

Read-onlyIdempotent

Read a public mainnet record for any wallet or player profile to retrieve creation dates, faction enlistment, SAGE fleets, signature bands, and first/last activity without storing data.

Instructions

Read a public mainnet record for a wallet or a player profile: profiles, creation dates, faction enlistment, SAGE fleets still on the accounts, signature bands, and first and last activity. Read-only. The lookup runs on the server against the public mainnet RPC. Nothing is stored.

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

Input Schema

Name	Required	Description	Default
`address`	Yes	A wallet address or a player profile address.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 4, 2026

TDQS

A4/5.0

Behavior4/5

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

Beyond the read-only, idempotent, and non-destructive annotations, it discloses that the lookup runs server-side against the public mainnet RPC and that nothing is stored. These are useful execution and privacy details, though data freshness and failure behavior are not addressed.

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 opening sentence front-loads the purpose, accepted inputs, and data scope, while the remaining short sentences cover safety, execution, and retention. Despite the substantial field list, there is no significant filler.

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?

For a simple one-address read, the description supplies scope, network, execution location, and storage behavior, while annotations cover the safety profile. With no output schema, however, the enumerated contents do not establish the response structure or behavior for unknown or inactive addresses, and sibling boundaries remain implicit.

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?

The sole address parameter is already fully described in the schema, and the description repeats that it can be a wallet or player-profile address. It adds no further format, resolution, or validation guidance, so the high schema coverage leaves this at baseline.

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 uses a specific read verb and identifies the accepted subjects and record contents, including profiles, faction enlistment, SAGE fleets, and activity dates. It does not explicitly differentiate this aggregate legacy lookup from siblings such as player_story or profile_key_audit.

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?

It gives a clear use context: retrieving public mainnet legacy information for either a wallet or a player-profile address. It offers no explicit when-not guidance or alternatives for narrower fleet, story, or key-audit requests.

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