Realtap

A wallet's trades in an NFT collection

get_nft_wallet_trades

Read-onlyIdempotent

The entries (purchases) and exits (sales) of one wallet in one NFT collection: asset, price (ADA), time and transaction. Entries are found by the wallet's stake key, exits through the listings it made; the answer says what it does not cover.

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": {
      "policyId": "<policyId>",
      "address": "<address>"
    },
    "name": "get_nft_wallet_trades"
  }
}

Input Schema

Name	Required	Description	Default
`address`	Yes	addr1… or stake1… address.
`policyId`	Yes	NFT policy id: 56 hex characters. Get it from `search` or `list_nft_collections`.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A3.9/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 behavior. The description adds meaningful non-obvious context: entries are found via the wallet's stake key, exits only through listings the wallet made, and the answer discloses what is not covered. That coverage caveat is valuable behavioral transparency, though pagination/rate-limit details are absent.

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 description is compact, front-loaded, and defines entries/exits inline without filler. The phrasing is somewhat dense but every clause carries information.

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 must convey return content; it lists asset, price, time, and transaction, and adds an explicit incompleteness caveat. It is complete enough for a read-only lookup, though ordering or pagination behavior is not mentioned.

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%, with both address and policyId documented including format and source. The description only adds that entries are matched by the wallet's stake key, which helps explain address handling, but it does not add policyId semantics.

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 resource and scope: entries and exits of one wallet in one NFT collection, and it enumerates returned fields (asset, ADA price, time, transaction). It clearly distinguishes this from broad sibling tools like get_recent_trades or get_nft_listings by limiting to wallet+collection.

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 wallet+collection scope implies when to use it, but there is no explicit when-to-use/when-not guidance and no named alternatives among siblings such as get_wallet_activity, get_recent_trades, or get_nft_listings. Adequate but leaves selection reasoning to inference.

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

All Realtap tools Inspect

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

Need Help?