Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

coingecko_search

Search CoinGecko by query to find coins, categories, markets, NFT contracts, asset platforms, and posts, with up to 50 results per section.

Instructions

CoinGecko discovery search. Searches CoinGecko for the required query q and returns matches in separate sections: coins, categories, markets, nft_contracts, asset_platforms and posts, each up to limit rows (default 10, max 50). Every section is always an array, and a search with no matches returns empty arrays.

Input Schema

NameRequiredDescriptionDefault
qYesSearch query
limitNoRows per section to return, default 10, max 50

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does a good job on the return side: it discloses that results arrive in six named sections, that every section is always an array, and that a no-match search returns empty arrays rather than an error. It stops short of auth, rate-limit, or matching-semantics (exact vs fuzzy) disclosure, which is a real gap for a search tool.

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?

Three sentences, front-loaded with the tool's identity and role, then return shape, then the empty-result contract. No filler or repetition, though the opening "CoinGecko discovery search" mildly restates the tool name.

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?

There is no output schema, so the description must describe the return payload, and it does so thoroughly for a two-parameter tool: section names, array guarantees, and the empty-result case. What is missing is how the query is matched and what identifiers the results carry, which matters for chaining into the other coingecko tools.

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%, covering both `q` and `limit`, so the schema already documents them. The description restates the default of 10 and max of 50 and clarifies that `limit` is per-section rather than total, which is a marginal but genuine clarification. Baseline 3 applies when the schema does the heavy lifting.

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 ("CoinGecko discovery search... searches CoinGecko for the required query `q`") and enumerates exactly what is returned across six named sections. An agent can tell this is the cross-entity lookup rather than a single-resource tool like coingecko_coin or coingecko_markets, though the description never explicitly names those siblings.

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?

"Discovery search" implies a broad find-something entry point, but there is no explicit when-to-use guidance, no statement that it is for resolving names to IDs before calling the detail endpoints, and no exclusion of alternatives. Usage is inferable but not stated.

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

Deploy Server

Other Tools