Skip to main content
Glama
Sign In

DeskCrew - AI Chatbot, Helpdesk & Knowledge base

by io.deskcrew
OverviewDiscussionsAdmin

nft_pumps

Today's pumps board for one chain: up to ten tokens with momentum from the DEX source's boosted list, ranked by a published score (0.6 volume acceleration, 0.4 price change over 24h), each with price, change, liquidity, volume, score and risk flags (thin liquidity under 20k USD, pair under 24h old). Each row may carry an 'Open in ' referral link, disclosed in its label; show it as is. Cached ten minutes. Most new tokens go to zero. Read-only market data; not financial advice. [price: $0.02]

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": {
      "chain": "<chain>"
    },
    "name": "nft_pumps"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayNoOnly today's board is available through this tool. Yesterday's board comes with a DeskCrew Pro workspace: use /nft flip or /coin pumps with day yesterday in your Discord server, or the NFT and Coins areas of the dashboard.
chainYesThe chain to rank: base, ethereum, polygon, avalanche, sei, solana or bsc.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / day / description
      Previous value: -"Only today's board is available through this tool. Yesterday's board comes with a DeskCrew Pro workspace: use /flip or /pumps with day yesterday in your Discord server, or the NFT area of the dashboard."New value: +"Only today's board is available through this tool. Yesterday's board comes with a DeskCrew Pro workspace: use /nft flip or /coin pumps with day yesterday in your Discord server, or the NFT and Coins areas of the dashboard."
  2. Added

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so richly: it discloses the ten-token cap, ranking formula, risk flags, referral-link labeling, ten-minute cache, read-only market-data status, and a strong volatility warning. It also clarifies that referral links should be shown as-is, which is useful invocation context.

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 description is dense but front-loaded, starting with the core resource and scope before adding ranking, fields, cache behavior, referral guidance, and risk warnings. Every sentence contributes operational or interpretive value, with no redundant restatement of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only data-board tool with no output schema and no annotations, the description is complete enough to call correctly: it explains the selection universe, ranking, fields, caching, risk caveats, and referral-link handling. Nothing essential about invocation or interpretation is missing.

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%, so the schema already documents both the chain and day parameters, including enum values and the fact that only today's board is available. The description reinforces 'one chain' and 'Today's' but adds no syntax or format detail beyond what the schema provides; baseline 3 is appropriate.

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: today's pumps board for a single chain, drawn from a DEX boosted list and ranked by a defined score. It also names the row fields and risk flags, so an agent can distinguish this from nft_floor, nft_price, nft_wallet, or nft_flips without opening the schema.

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?

Usage is implied by 'Today's pumps board' and the chain parameter, but the description does not explicitly say when to choose this tool over related siblings such as nft_flips or nft_floor. It also does not state when not to use it, aside from the schema-level note that yesterday's board requires a Pro workspace.

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

All DeskCrew - AI Chatbot, Helpdesk & Knowledge base 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