Skip to main content
Glama

DYOE Trending Coins ($0.01)

dyoe_trending
Read-only

Fetch currently trending coins for trading and research agents to spot market momentum. Costs $0.01 USDC on Base per call via x402.

Instructions

The coins trending right now — for trading & research agents. Input: (none) Price: $0.01 USDC on Base per call, paid via x402.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), and the description adds critical operational context beyond them: this call costs $0.01 USDC on Base and is settled via x402. That payment requirement is exactly the kind of behavior an agent must know before invoking. It does not describe return shape or data freshness beyond 'right now'.

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?

Two short sentences, front-loaded with the resource and purpose, then the empty input and price. No wasted text, though the pricing details are compressed into a somewhat dense clause.

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 zero-param, read-only, paid tool with no output schema, the description covers purpose, inputs, and cost. The only real gap is what the response contains and how 'trending' is scoped, which an agent would have to discover on first call.

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?

Zero parameters, so the baseline is 4. The description explicitly confirms 'Input: (none)', which reinforces the empty schema and removes any doubt about required arguments.

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 resource ('coins trending right now') with a clear read-oriented purpose. It doesn't explicitly differentiate from similarly themed siblings such as dyoe_movers or dyoe_market, so it falls short of 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?

The audience phrase 'for trading & research agents' implies when the tool is useful, but there is no when-to-use vs. when-not guidance and no named alternative among the many market/coin siblings. Usage is implied, not specified.

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