AIXBT

Find crypto projects

list_projects

Read-only

Find tracked crypto Projects using supported filters.

Input Schema

Name	Required	Description
`ids`	No	Comma-separated Project IDs
`sort`	No	Use rank for the canonical top-project leaderboard (ranked projects only, confidence band before score). trend sorts raw score (default); createdAt and reinforcedAt sort by time.
`chain`	No	Chain to filter by (e.g. "ethereum", "solana")
`limit`	No	Number of results to return (default and maximum: 50)
`names`	No	Comma-separated Project names
`slugs`	No	Comma-separated Project slugs
`cursor`	No	Cursor returned in meta.nextCursor from the previous page
`address`	No	Token contract address
`tickers`	No	Comma-separated tickers
`minTrend`	No	Minimum current trend measurement
`universe`	No	Market universe (default: crypto)
`xHandles`	No	Comma-separated X handles
`assetTypes`	No	Comma-separated asset types (token, stablecoin, nft-collection)
`categories`	No	Comma-separated Project category slugs; use get_vocabulary to list them

Output Schema

Name	Required	Description	Default
`data`	Yes
`meta`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 16, 2026

changedInput schema / properties / sort / description

Previous value: -"Order by trend (default), creation time, or latest reinforcement"New value: +"Use rank for the canonical top-project leaderboard (ranked projects only, confidence band before score). trend sorts raw score (default); createdAt and reinforcedAt sort by time."

changedInput schema / properties / sort / enum

Previous value: -[
-  "trend",
-  "createdAt",
-  "reinforcedAt"
-]New value: +[
+  "rank",
+  "trend",
+  "createdAt",
+  "reinforcedAt"
+]

changedInput schema / properties / universe / enum

Previous value: -[
-  "crypto",
-  "tradfi"
-]New value: +[
+  "crypto"
+]

addedOutput schema / properties / data / items / properties / rankBand

Added value: +{
+  "enum": [
+    "strong",
+    "corroborated"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / data / items / properties / universe / enum
```
Previous value: -[
-  "crypto",
-  "tradfi"
-]New value: +[
+  "crypto"
+]
```

Changed5 schema fields changedAug 17, 2026

removedInput schema / properties / minEmergence

Removed value: -{
-  "description": "Minimum current emergence measurement; currently returns an empty page while recalibrating",
-  "type": "number"
-}

changedInput schema / properties / sort / description

Previous value: -"Order by trend (default), emergence, creation time, or latest reinforcement; emergence currently returns an empty page while recalibrating"New value: +"Order by trend (default), creation time, or latest reinforcement"

changedInput schema / properties / sort / enum

Previous value: -[
-  "trend",
-  "emergence",
-  "createdAt",
-  "reinforcedAt"
-]New value: +[
+  "trend",
+  "createdAt",
+  "reinforcedAt"
+]

removedOutput schema / properties / data / items / properties / emergence
```
Removed value: -{
-  "type": "number"
-}
```
removedOutput schema / properties / data / items / properties / emergenceRank
```
Removed value: -{
-  "type": "number"
-}
```

Changed2 schema fields changedAug 14, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed2 schema fields changedAug 12, 2026

changedInput schema / properties / minEmergence / description

Previous value: -"Minimum current emergence measurement"New value: +"Minimum current emergence measurement; currently returns an empty page while recalibrating"

changedInput schema / properties / sort / description

Previous value: -"Order by trend (default), emergence, creation time, or latest reinforcement"New value: +"Order by trend (default), emergence, creation time, or latest reinforcement; emergence currently returns an empty page while recalibrating"

Changed5 schema fields changedAug 12, 2026

addedInput schema / properties / minEmergence

Added value: +{
+  "description": "Minimum current emergence measurement",
+  "type": "number"
+}

changedInput schema / properties / sort / description

Previous value: -"Order by trend (default), creation time, or latest reinforcement"New value: +"Order by trend (default), emergence, creation time, or latest reinforcement"

changedInput schema / properties / sort / enum

Previous value: -[
-  "trend",
-  "createdAt",
-  "reinforcedAt"
-]New value: +[
+  "trend",
+  "emergence",
+  "createdAt",
+  "reinforcedAt"
+]

addedOutput schema / properties / data / items / properties / emergence
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / data / items / properties / emergenceRank
```
Added value: +{
+  "type": "number"
+}
```

Changed4 schema fields changedAug 10, 2026

removedInput schema / properties / hasToken

Removed value: -{
-  "description": "Only include Projects with (true) or without (false) a token",
-  "type": "boolean"
-}

changedInput schema / properties / minTrend / description

Previous value: -"Minimum current trend score from 0 to 100"New value: +"Minimum current trend measurement"

removedInput schema / properties / minTrend / maximum
```
Removed value: -100
```
removedInput schema / properties / minTrend / minimum
```
Removed value: -0
```

Changed8 schema fields changedAug 9, 2026

changedInput schema / properties / categories / description

Previous value: -"Comma-separated canonical category slugs"New value: +"Comma-separated Project category slugs; use get_vocabulary to list them"

changedInput schema / properties / cursor / description

Previous value: -"Opaque cursor from a previous page (meta.nextCursor)"New value: +"Cursor returned in meta.nextCursor from the previous page"

addedInput schema / properties / hasToken / description

Added value: +"Only include Projects with (true) or without (false) a token"

changedInput schema / properties / ids / description

Previous value: -"Comma-separated Project ids"New value: +"Comma-separated Project IDs"

changedInput schema / properties / limit / description

Previous value: -"Results per page (default: 50, max: 50)"New value: +"Number of results to return (default and maximum: 50)"

changedInput schema / properties / minTrend / description

Previous value: -"Minimum canonical trend measurement"New value: +"Minimum current trend score from 0 to 100"

changedInput schema / properties / sort / description

Previous value: -"Sort field (default: trend)"New value: +"Order by trend (default), creation time, or latest reinforcement"

addedInput schema / properties / universe / description
```
Added value: +"Market universe (default: crypto)"
```

First observedAug 9, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety and scope are covered. The description only adds the 'tracked' qualifier on the project universe; it says nothing about pagination behavior or result ordering, though the schema's cursor and sort fields partially cover that. With annotations carrying the safety profile, this is a modest add.

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?

A single front-loaded sentence with no filler, which is efficient for a filter-driven list tool. It is arguably too thin for a 14-parameter tool, but nothing is redundant or buried.

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?

With 100% schema coverage, an output schema, and annotations, the structured data carries most of the load. However, for a 14-parameter listing tool, the description omits that all filters are optional and combinable, and gives no sense of what a result set contains beyond the output schema.

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% across all 14 parameters, so the schema already documents filter syntax, sort semantics, and pagination. The description adds nothing beyond 'supported filters', so the baseline 3 for high-coverage schemas 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 (Find) and resource (tracked crypto Projects) with scope 'tracked' and the mechanism 'using supported filters'. It is clear what the tool does, but it does not distinguish itself from siblings like get_project or list_clusters, leaving the agent to infer that this is the multi-result listing tool.

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?

The phrase 'using supported filters' gestures at usage but gives no when-to-use guidance, no alternatives (e.g. get_project for a single project, get_vocabulary for category slugs), and no exclusions. An agent gets no help choosing this over the other 11 sibling tools.

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

All AIXBT 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?