Skip to main content
Glama
Sign In

Realtap

by io.github.CSteenkamp
OverviewDiscussionsAdmin

NFTs for sale in a collection

get_nft_listings
Read-onlyIdempotent

Active marketplace listings of an NFT collection: asset name, price (ADA), marketplace, rarity rank when known, seller and listing time. Use it to find the cheapest or rarest NFTs currently for sale.

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>"
    },
    "name": "get_nft_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoprice = cheapest first, recent = newest first, rarity = rarest first.price
limitNoHow many listings to return (1-50, default 10).
cursorNoValue of `nextCursor` from the previous call, to get the next page.
policyIdYesNFT policy id: 56 hex characters. Get it from `search` or `list_nft_collections`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the description's job is narrower. It adds real value by scoping results to *active* listings only, noting the data is 'when known' (rarity may be absent), and listing the exact returned fields — all behavior you could not infer from the annotations.

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?

Two sentences, zero waste: the first defines the resource and its payload, the second front-loads the intended use case. No repetition of schema or annotation content.

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 usefully enumerates the returned fields (asset name, price, marketplace, rarity, seller, listing time), which is exactly what an agent needs to trust the return shape. Pagination is only covered by the schema's cursor field and the description never signals result limits or empty-result behavior, leaving a small gap.

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% and the sort enum, limit bounds, and cursor semantics are fully documented in the schema, so baseline 3 applies. The description contributes no additional parameter guidance (e.g., guidance on cursor chaining or sort + limit interaction) beyond what the schema already says.

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?

States a specific verb and resource — 'Active marketplace listings of an NFT collection' — and enumerates what each listing contains, so an agent can distinguish it from metadata siblings like get_nft_collection or aggregate siblings like get_nft_market/analytics. It stops short of naming any sibling explicitly to route the agent, so it lands at 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 Guidelines4/5

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

'Use it to find the cheapest or rarest NFTs currently for sale' gives a concrete task-level trigger that maps directly onto the sort enum. There is no explicit when-not or named alternative for related needs (floor history, trait prices, wallet trades), so it is clear context without exclusions.

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

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