Skip to main content
Glama

solenrich

by io.github.0xSardius
OverviewDiscussionsAdmin

StonkFun Reward-Coin Screener

stonk_screener

Screen every StonkFun reward coin with payout status (PAYING / STALE / NEVER), a live flag (traded AND paid in 24h), and the round-trip transfer-tax cost per row. Filters: quote mint, category, holders, age (min/max), 24h volume, market cap, paying_only, live_only. Sort by volume24h (default), lastPayout, holders, priceChange24h, yield7d, yield30d, rewardsUsd. Use for "which coins on NVDAX paid holders today?" or "live xStock coins under $1M". Served from a 10-minute ingest. Use stonk_gems for a ranked shortlist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoRanking keyvolume24h
limitNoRows to return
categoryNoQuote category filter
live_onlyNoOnly coins that traded AND paid in the last 24h
quote_mintNoOnly coins paired against this quote mint
min_holdersNoMinimum reward-receiving holders
paying_onlyNoOnly coins that paid holders in the last 24h
max_age_daysNoMaximum coin age in days
min_age_daysNoMinimum coin age in days
max_market_cap_usdNoMaximum market cap in USD
min_volume_24h_usdNoMinimum 24h volume in USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / live_only
      Added value: +{
+  "default": false,
+  "description": "Only coins that traded AND paid in the last 24h",
+  "type": "boolean"
+}
    • addedInput schema / properties / max_age_days
      Added value: +{
+  "description": "Maximum coin age in days",
+  "minimum": 0,
+  "type": "number"
+}
    • addedInput schema / properties / max_market_cap_usd
      Added value: +{
+  "description": "Maximum market cap in USD",
+  "minimum": 0,
+  "type": "number"
+}
    • addedInput schema / properties / min_volume_24h_usd
      Added value: +{
+  "description": "Minimum 24h volume in USD",
+  "minimum": 0,
+  "type": "number"
+}
    • addedInput schema / properties / paying_only
      Added value: +{
+  "default": false,
+  "description": "Only coins that paid holders in the last 24h",
+  "type": "boolean"
+}
    • changedInput schema / properties / sort / default
      Previous value: -"rewardsUsd"New value: +"volume24h"
    • changedInput schema / properties / sort / enum
      Previous value: -[
-  "yield7d",
-  "yield30d",
-  "rewardsUsd",
-  "volume24h"
-]New value: +[
+  "yield7d",
+  "yield30d",
+  "rewardsUsd",
+  "volume24h",
+  "lastPayout",
+  "holders",
+  "priceChange24h"
+]
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses meaningful traits: the three payout statuses, the precise live-flag definition (traded AND paid in 24h), and the 10-minute ingest freshness window. It stops short of a 5 only because it omits minor operational details like rate limits or default-row-count behavior.

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 core value proposition is front-loaded, and the filter/sort lists are compactly packed. It is dense, and some enumeration is redundant with the schema, but every sentence earns its place, including the freshness note and the sibling routing.

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?

Given no output schema and no annotations, the description adequately explains the return shape, available sort keys, data freshness, and example intents. The main gaps are the units of the round-trip transfer-tax cost and explicit pagination/limit behavior, but overall it is complete for a complex 11-parameter tool.

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%, so the schema fully documents all 11 parameters. The description's filter and sort enumeration mostly restates schema content, adding little semantic value beyond framing which filters matter for the example queries. 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?

States a specific verb ('Screen'), the exact resource ('every StonkFun reward coin'), and what each returned row contains (payout status, live flag, transfer-tax cost). It also names the sibling it is not ('Use stonk_gems for a ranked shortlist'), so an agent can differentiate without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives explicit when-to-use context with two concrete natural-language queries ('which coins on NVDAX paid holders today?', 'live xStock coins under $1M') and routes to an alternative tool for a different use case. Nothing is left to inference.

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

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