sa-ecosystem-node

Player story

player_story

Read-onlyIdempotent

Instructions

Turn a public player_legacy card into a short plain-language story, only after that wallet opts in. The wallet signs a fixed sentence, and an allowlisted hub signer publishes it as a story-optin update. Without a valid unrevoked opt-in the tool returns not opted in and does not tell the story. Read-only. The story does not quote names, prices, or a call to action.

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_story"
  }
}

Input Schema

Name	Required	Description	Default
`address`	Yes	The wallet that signed the opt-in, or a player profile address that signed one.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 4, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses the opt-in signing flow, the allowlisted hub signer publishing as a story-optin update, and the exact failure behavior when no valid opt-in exists. It also states privacy constraints (no names, prices, or call to action), which annotations could never convey.

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?

The gating condition is front-loaded in the first sentence and each subsequent sentence adds a distinct fact about signing, publication, failure, and privacy. It is slightly dense with protocol detail but has no 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 one-parameter tool with no output schema, the description covers the prerequisite, the publication mechanism, the failure mode, and the content limits, which is most of what an agent needs. Missing only an explicit indication of what the returned story payload looks like, though the content constraints imply its shape.

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 in the schema itself, including that it is the signing wallet or a player profile address. The description only reinforces that the same wallet must have opted in, adding little syntax or format detail beyond the schema.

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?

The description states a specific verb and resource: turning a public player_legacy card into a short plain-language story. It explicitly ties itself to the player_legacy sibling as the input source, so an agent can distinguish the two without inspecting either schema.

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 precondition for use: the wallet must have opted in, and without a valid unrevoked opt-in the tool returns not opted in. It does not explicitly say to call player_legacy first or name an alternative path for non-opted-in wallets, so the when-not guidance is present but not exhaustively routed.

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