Moralis MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the default behavior (cross-chain results including Solana) and optional filtering by chain, which adds useful context. However, it lacks details on rate limits, authentication needs, pagination (implied by the limit parameter but not explained), or what 'trending' specifically entails (e.g., time frame, algorithm). For a tool with no annotations, this leaves gaps in understanding its operational behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and well-structured, consisting of two sentences that efficiently convey key information: the tool's purpose and its usage guidelines. Every sentence earns its place, with no wasted words, and it is front-loaded with the core functionality. This makes it easy for an AI agent to quickly grasp the tool's intent and parameters.

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

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

Given the complexity of a trending tokens tool with 2 parameters, no annotations, and no output schema, the description is moderately complete. It covers the purpose and basic usage but lacks details on behavioral aspects like rate limits, authentication, or output format. While it compensates somewhat by explaining the chain parameter's semantics, it doesn't fully address the gaps left by the absence of annotations and output schema, making it adequate but with room for improvement.

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

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

The input schema has 100% description coverage, with both parameters ('chain' and 'limit') well-documented in the schema itself. The description adds value by explaining the default cross-chain behavior and optional filtering by 'chain', which clarifies the semantic use of the chain parameter beyond the enum list. However, it doesn't provide additional details on the 'limit' parameter or any constraints not already in the schema. Given the high schema coverage, a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'List top tokens trending based on trading activity, volume, liquidity and more.' It specifies the verb ('List') and resource ('top tokens trending'), and mentions the criteria (trading activity, volume, liquidity). However, it doesn't explicitly differentiate from sibling tools like 'evm_gettopgainerstokens' or 'evm_gettoploserstokens', which might also involve trending or performance metrics, leaving some ambiguity.

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

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

The description provides clear usage context: 'By default this returns cross-chain results, including Solana. Optionally filter by `chain` for single chain results.' This indicates when to use the tool (for trending tokens across chains or filtered by chain) and implies an alternative (using the chain parameter for single-chain results). However, it doesn't explicitly state when not to use it or compare it to other trending-related siblings, such as 'evm_gettopcryptocurrenciesbytradingvolume', which might overlap in functionality.

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