Skip to main content
Glama

AIXBT

by io.github.aixbt

Find crypto projects

list_projects
Read-only

Find tracked crypto Projects using supported filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoComma-separated Project IDs
sortNoOrder by trend (default), creation time, or latest reinforcement
chainNoChain to filter by (e.g. "ethereum", "solana")
limitNoNumber of results to return (default and maximum: 50)
namesNoComma-separated Project names
slugsNoComma-separated Project slugs
cursorNoCursor returned in meta.nextCursor from the previous page
addressNoToken contract address
tickersNoComma-separated tickers
minTrendNoMinimum current trend measurement
universeNoMarket universe (default: crypto)
xHandlesNoComma-separated X handles
assetTypesNoComma-separated asset types (token, stablecoin, nft-collection)
categoriesNoComma-separated Project category slugs; use get_vocabulary to list them

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
metaYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changed
    • 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"
-}
  2. Changed2 schema fields changed
    • 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"
  3. Changed2 schema fields changed
    • 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"
  4. Changed5 schema fields changed
    • 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"
+}
  5. Changed4 schema fields changed
    • 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
  6. Changed8 schema fields changed
    • 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)"
  7. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, indicating safe reads. The description adds no behavioral traits beyond stating it uses filters; but with 14 parameters and no mention of pagination, rate limits, or result completeness, the description does not significantly augment the annotation-provided safety profile.

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 description is short and front-loaded. Every word serves a purpose, but the phrase 'using supported filters' is redundant given the schema already enumerates filter parameters. A slight edge toward clarity could exist.

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?

Given the tool has 14 parameters with 100% schema coverage, a rich output schema, and annotations clearly stating it's read-only and non-destructive, the description captures the core intent. It is adequate for contextual completeness without needing to detail every filter.

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%, so each parameter is already documented in the schema. The description adds no new meaning beyond restating that filters are supported. The baseline of 3 is appropriate since the schema handles the burden fully.

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?

The description clearly states the tool lists tracked crypto projects using filters. The verb 'Find' and resource 'tracked crypto Projects' are specific, but the phrase 'using supported filters' is vague and does not distinguish from siblings like 'get_project', which retrieves a single project by ID.

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 usage for filtering projects but provides no explicit guidance on when to use this tool versus alternatives like 'get_project' for a single project or other list tools. Without exclusions or when-not-to-use instructions, the agent must infer context from sibling names.

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

All AIXBT toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation5/5

Each tool targets a distinct entity or action: single vs. list (get vs. list), intel vs. project vs. topic vs. report vs. cluster vs. vocabulary vs. credential check. No two tools have overlapping purposes; the descriptions clearly differentiate them.

Naming Consistency5/5

Uses a consistent pattern: get_ for singular retrieval, list_ for plural searches/listing. Only 'me' deviates, but it's a standard name for credential checks. The pattern is predictable and easy to follow.

Tool Count5/5

12 tools cover a focused domain (crypto intelligence) without unnecessary bloat. Each tool earns its place: core entities (projects, topics, intel), plus series, reports, vocabulary, clusters, and auth check. The count feels well-scoped.

Completeness5/5

The server provides a complete read surface for its domain: listing, searching, getting details, historical series, reports, and filter metadata. No obvious gaps for consuming intelligence (CRUD not expected in a read-only API).

Resources