Skip to main content
Glama

canton-ccpedia

by io.github.UnityNodes
OverviewDiscussionsAdmin

list_ecosystem_projects

Read-onlyIdempotent

List Canton Network ecosystem projects (DeFi protocols, wallets, custody, infrastructure, NaaS, etc.) from the curated canton.wiki catalog. Filter by category or free-text query. Returns name, category, description and URL: a static directory of who-builds-on-Canton, not live on-chain/TVL data (use get_token_market for live DeFi TVL). Canton-only.

Input Schema

NameRequiredDescriptionDefault
limitNoHow many projects to return. Default 30, max 100. The response states the full count.
queryNoSearch in title/description/tags
offsetNoSkip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.
categoryNoFilter by category (e.g. "DeFi", "Wallets", "NaaS")
livenessNoRestrict to projects whose site last responded this way to CCPEDIA's daily probe. Omit for all of them; every row is labelled either way.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"How many projects to return. Default 30, max 100. The response states the full count."
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / liveness
      Added value: +{
+  "description": "Restrict to projects whose site last responded this way to CCPEDIA's daily probe. Omit for all of them; every row is labelled either way.",
+  "enum": [
+    "alive",
+    "suspect",
+    "dead",
+    "unknown"
+  ],
+  "type": "string"
+}
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuinely non-structured context: the data is a curated static catalog rather than live on-chain/TVL data, it is Canton-only, and it lists the returned fields. It stops short of describing pagination/count behaviour, which is left to the schema.

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

Conciseness5/5

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

Three tight sentences with the core purpose front-loaded, followed by filtering capability, return shape and the disambiguation note. Every clause carries information; there is no filler.

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?

With no output schema, the description compensates by naming the returned fields, and it flags the static-vs-live data boundary and Canton-only scope. Paging and the liveness-labelling behaviour are covered only by the schema, so an agent relying on the description alone would miss those, leaving a small gap.

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 the schema already documents limit, offset, query, category and the liveness enum with defaults and bounds. The description only restates that filtering is possible by category or free text, adding no syntax, format or semantics beyond the schema. 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.

Purpose5/5

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

States a specific verb (List) plus resource (Canton Network ecosystem projects) and names the concrete source catalog (canton.wiki). It also enumerates the project types covered (DeFi, wallets, custody, infrastructure, NaaS) and names the return fields, so an agent can distinguish it from siblings like get_token_market or find_similar_projects without opening a schema.

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

Usage Guidelines4/5

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

Explicitly scopes the tool as a static directory and routes live DeFi TVL queries to get_token_market, which is a real alternative with a stated condition. It does not, however, address overlap with near-neighbours such as find_similar_projects, list_featured_apps or get_ecosystem_gaps, so usage guidance is clear but not exhaustive.

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

All canton-ccpedia toolsInspect
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