Skip to main content
Glama

ArcanumFleet Trending Solana Mints

arcanum_trending_mints
Read-onlyIdempotent

Use this to discover the top 10 trending Solana token mints by DexScreener boost and momentum activity. Costs 0.002 USDC via x402.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and open-world behavior, so the safety profile is covered. The description adds genuinely non-obvious behavior not in the annotations: the call costs 0.002 USDC via x402 (a payment prerequisite an agent must know) and returns a bounded set of 10 items. It stops short of describing response fields or failure modes.

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 short sentences, zero filler, with the core purpose front-loaded and the cost constraint appended. Every clause carries information an agent needs.

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?

For a parameterless read-only tool with no output schema, the definition covers purpose, ranking basis, result cardinality, and cost — enough to invoke it correctly. Only the shape of the returned mint records is left unspecified, which is a minor gap given no output schema exists.

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 there is no schema semantics to enrich and the baseline of 4 applies. The description correctly implies the call is parameterless by describing a fixed top-10 result.

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 ('discover the top 10 trending Solana token mints') and even names the ranking signal (DexScreener boost and momentum activity), so an agent knows exactly what it returns. It does not explicitly differentiate itself from fuzzy siblings such as arcanum_pulse or arcanum_smart_money, which keeps it from a 5.

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?

'Use this to discover...' gives an implied usage context but no when-to-use vs. when-not guidance and names no alternative for overlapping needs like social or smart-money signals. The paid-call note is helpful context but not selection guidance.

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