Skip to main content
Glama

JestSprout Meme Coin & Solana Rug-Check Tools

Trending Solana memecoin themes & narratives

trending_memecoin_narratives
Read-onlyIdempotent

FREE, no API key (about 100 calls/day). Current trending meme coin themes, narratives and keywords on Solana, taken from DexScreener's top-boosted tokens and recent JestSprout ideas. Includes the boosted coins list. Cached about 15 minutes.

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": "trending_memecoin_narratives"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuinely non-obvious operational traits: a daily quota (~100 calls), an external data dependency, and a ~15-minute cache freshness window. Only the limit behavior on quota exhaustion is unstated.

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 compact sentences, front-loaded with the cost/access constraint and then the data scope and freshness. Every clause carries usable information with no filler.

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 sketch the return value; it says themes, narratives, keywords, and an included boosted-coins list, which is adequate. The structure/shape of the returned themes (list vs ranked vs categories) remains only loosely implied, a minor gap for a data-fetching tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. It correctly avoids inventing parameter discussion.

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 names the specific resource ('trending meme coin themes, narratives and keywords on Solana') plus its provenance (DexScreener top-boosted tokens, JestSprout ideas). That makes it clearly distinct from generation siblings like generate_coin_concept or memecoin_name_ticker_ideas.

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?

Implicit usage context is present: 'FREE, no API key (about 100 calls/day)' and 'Cached about 15 minutes' tell an agent it is cheap to call but should not be spammed. However, it never says when to prefer it over siblings or what to do when the cache is stale or the daily quota is exhausted.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources