@thryx/mcp-server

thryx_trending

Identify tokens with the most trading activity over the last 6 hours to reveal top conviction signals. Use optional limit to control the number of results.

Instructions

Tokens with the most trading activity in the last 6 hours. Top conviction signals.

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

Input Schema

Name	Required	Description	Default
`limit`	No	How many to return. 1–20, default 10.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.0Aug 4, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It states it returns tokens with high trading activity, but the phrase 'top conviction signals' is ambiguous and undefined. It does not clarify how conviction is measured, whether rankings refresh, or what fields are returned. This leaves the agent uncertain about the tool's output semantics.

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 two short sentences, front-loading the core purpose and adding a hint of unique value ('top conviction signals'). No wasted words; it is appropriately sized for such a simple tool.

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

Completeness3/5

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

Given the low complexity and full schema coverage, the description gives the essential purpose. However, the undefined term 'conviction signals' and the lack of information about the return format (e.g., token names, addresses, metrics) leave the agent guessing about what data it will receive. Without annotations or output schema, more detail would be helpful.

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?

The input schema fully documents the only parameter 'limit' with a clear description ('How many to return. 1–20, default 10.'). The tool description adds no extra parameter information, but since schema coverage is 100%, baseline 3 applies.

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 clearly states the resource (tokens) and the criterion (most trading activity in the last 6 hours). This distinguishes it from siblings like thryx_recent_tokens (likely recent listings) and thryx_token_of_day (daily pick) by specifying the time window and activity focus.

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 description implies use for discovering currently active tokens (trending), but provides no explicit guidance on when to choose this over similar tools like thryx_leaderboard or thryx_recent_tokens. No alternatives are named and no exclusions are stated.

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