AIsa Finance

Trending Search List

get_coingecko_search_trending

Read-onlyIdempotent

This endpoint allows you query trending search coins, NFTs and categories on CoinGecko in the last 24 hours

Published reference price: $0.008 USD per successful request. Declared unit rate: $0 USD per provider_credit. Account-specific pricing and final settlement may differ.

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

Input Schema

Name	Required	Description	Default
`show_max`	No	Show max number of results available for the given type. Available values: `coins`, `nfts`, `categories` e.g. `coins` or `coins,nfts,categories`

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

addedInput schema / properties / show_max

Added value: +{
+  "description": "Show max number of results available for the given type. \nAvailable values: `coins`, `nfts`, `categories` \ne.g. `coins` or `coins,nfts,categories`",
+  "type": "string"
+}

First observedSep 15, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description usefully adds the 24-hour time window, but says nothing about rate limits, freshness guarantees, or result ordering beyond that.

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?

The core description is a single front-loaded sentence that states purpose and scope efficiently. The embedded pricing boilerplate adds some noise but is bounded and clearly demarcated.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. For a zero-required-parameter read tool, the description is nearly complete; only the missing alternative-tool routing keeps it from a top score.

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?

Schema description coverage is 100%, with show_max fully documented including its enum-like accepted values, so the schema carries the parameter burden. The description adds no parameter meaning beyond what the schema provides, so baseline 3 applies.

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: 'query trending search coins, NFTs and categories', with the temporal scope ('last 24 hours') made explicit. This is clearly distinguishable from list/market siblings by the 'trending search' framing, though it does not name any sibling to contrast against.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance. An agent is left to infer that this is for surfacing currently-trending assets; alternatives like get_coingecko_coins_list, get_coingecko_coins_markets, or search are never mentioned as differentiators.

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

All AIsa Finance tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?