Skip to main content
Glama
Sign In

Realtap

by io.github.CSteenkamp
OverviewDiscussionsAdmin

Rank NFT collections

list_nft_collections
Read-onlyIdempotent

Ranked list of Cardano NFT collections with floor price (ADA and USD), 24 h floor change (percent), volume (ADA, 24 h and 7 d), sales, listings, supply and holders. Use it for "top NFT collections" questions or to find a collection by name.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_nft_collections"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoOrdering.volume24h
limitNoHow many collections to return (1-50, default 10).
queryNoOnly collections whose name contains this text, or whose policy id starts with it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 and open-world behavior, so the safety profile is covered. The description adds real value by enumerating the returned fields (floor in ADA and USD, 24h change, volume windows, sales, listings, supply, holders), which matters since there is no output schema. It does not mention result ordering defaults or pagination, hence not a 5.

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, both earning their place: the first front-loads the returned data, the second front-loads the use cases. No filler or restatement of the title.

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 return-shape burden and does so by listing the fields. It is slightly thin on ordering behavior (default volume24h, 'new' sort) and on how results rank, but everything needed to invoke it correctly is present.

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 all three parameters (sort, limit, query) are documented in the schema, including the enum ordering and the name/policy-id matching rule. The description adds no parameter-level detail beyond that, so the baseline 3 applies.

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?

States a concrete verb and resource ('Ranked list of Cardano NFT collections') and immediately enumerates the metrics returned, so its scope is unambiguous. The ranked-list framing also separates it from point-lookup siblings like get_nft_collection.

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?

Gives explicit trigger scenarios: 'top NFT collections' questions and name-based collection lookup. It stops short of naming the alternative to use when the caller wants one collection's detail, so it is clear but not fully routing.

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