Skip to main content
Glama

canton-ccpedia

by io.github.UnityNodes

search

Read-onlyIdempotent

Keyword/full-text search over the Canton Network knowledge base (CIPs, Canton/Daml/Splice docs, forum, mailing lists, whitepapers, grant proposals, blog, YouTube, GitHub). Canton-specific. Do NOT use for other blockchains, the web, or local files. Use this for exact-term/name lookups; use semantic_search instead for conceptual or 'how does X work' questions, and get_doc to read a full page once you have its id. NOTE: forum matches cover the topic TITLE and the FIRST POST only; a term that appears only inside a forum reply will not surface here, so use semantic_search (which indexes all forum post bodies) when a forum discussion is likely and this returns nothing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoRestrict results to one source type; "governance" is the stated reasoning behind an on-chain DSO vote; "all" searches everythingall
limitNoMax results to return (1-50)
queryYesSearch query
offsetNoSkip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.

Schema Changelog

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

  1. Changed2 schema fields changed
    • changedInput schema / properties / type / description
      Previous value: -"Restrict results to one source type; \"all\" searches everything"New value: +"Restrict results to one source type; \"governance\" is the stated reasoning behind an on-chain DSO vote; \"all\" searches everything"
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "all",
-  "cip",
-  "doc",
-  "discussion",
-  "mail",
-  "whitepaper",
-  "proposal",
-  "blog",
-  "youtube",
-  "github"
-]New value: +[
+  "all",
+  "cip",
+  "doc",
+  "discussion",
+  "mail",
+  "whitepaper",
+  "proposal",
+  "blog",
+  "youtube",
+  "github",
+  "governance"
+]
  2. Changed1 schema field changed
    • 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. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Max results to return (1-50)"
    • addedInput schema / properties / type / description
      Added value: +"Restrict results to one source type; \"all\" searches everything"
  4. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the description only needs to add limits. It does: forum indexing only covers topic title and first post, and it exposes the exact consequence (terms in replies won't surface). This is useful beyond the annotations, though it doesn't cover response shape or rate limits.

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?

Front-loaded with the core function and Canton scope, then moves to exclusions, alternatives, and caveats. The source list is long but earns its place by defining what the knowledge base means, and no sentence is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a general read-only search tool, the description covers scope, exclusions, common alternatives, query intent, and a subtle indexing limitation. The schema handles parameter constraints and paging details, and annotations handle safety, so nothing needed to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage for all four parameters, so the baseline is 3. The description adds query-level guidance ('exact-term/name lookups') and clarifies a semantic limitation on search results, going a step beyond the schema's terse 'Search query' field text.

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 action (keyword/full-text search) over a defined resource (Canton Network knowledge base) and enumerates the covered source types. It contrasts itself with semantic_search and get_doc, so an agent can tell them apart without opening schemas.

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

Usage Guidelines5/5

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

Explicitly says when-not (other blockchains, web, local files), when-yes (exact-term/name lookups), and names alternatives (semantic_search for conceptual questions, get_doc after an id is known). It even gives a remediation path for a known recall gap: use semantic_search when a term may be in forum replies.

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
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
Disambiguation2/5

Many tools have overlapping search/retrieval functionality (search, semantic_search, full_context, search_community, search_github_issues, etc.), and the CIP-specific variants (get_cip, get_cip_history, get_cip_votes, get_cip_mentions, get_cip_citations) are numerous and subtly differentiated. Despite cross-references in the descriptions, the boundaries are fine-grained and an agent is likely to misselect among the 8+ search tools or the 8+ CIP tools.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (get_x, list_x, search_x, find_x). Mixed styles or camelCase are absent, and the verb choice (get, list, search, find, detect, compare) is semantically appropriate to each action, making the naming highly predictable.

Tool Count1/5

With 88 tools, the surface is extremely overgrown for a single server, far exceeding the 25+ 'too many' threshold and approaching the 50+ 'extreme mismatch' category. Even for a comprehensive ecosystem knowledge base, this creates a massive selection burden and makes the tool set unwieldy for agents.

Completeness5/5

The server covers the full Canton ecosystem: docs, forum, mailing lists, GitHub, CIPs, governance, validators, versions, deprecations, security, and media. There are no glaring gaps in the knowledge domain; every major resource type has retrieval and analysis tools, making the coverage exhaustive with no obvious dead ends.

Resources