Skip to main content
Glama

canton-ccpedia

by io.github.UnityNodes

semantic_search

Read-onlyIdempotent

PRIMARY tool for open-ended questions: how / why / what-is, troubleshooting a symptom ("why is my balance zero", "how do I fix X"), and locating config or setup steps. Conceptual/meaning-based search over the full Canton corpus (CIPs, docs, forum, mailing lists, proposals, blog, releases, ecosystem, foundation KB, YouTube) using vector+FTS hybrid retrieval with reranking. Canton-specific. Use this FIRST for anything a specific tool does not clearly own; the narrow curated tools (get_faq, find_known_issues, diagnose_error) cover only small hand-picked sets or need a literal error string, so prefer semantic_search for real how/why/config questions. Then call get_doc with a returned id to read the full source page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many chunks to return. Default 6, max 15. Capped at 2 per document so one long file cannot take every slot.
queryYesFree-form question or phrase.
source_typesNoRestrict to these source types. "proposal" is a Dev Fund grant request; "github_item" is an ordinary issue or PR from any other indexed repo; "sdk_version" is a released package version from the npm/Docker registries. Omit for all.

Schema Changelog

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

  1. Changed2 schema fields changed
    • changedInput schema / properties / source_types / description
      Previous value: -"Restrict to these source types. \"proposal\" is a Dev Fund grant request; \"github_item\" is an ordinary issue or PR from any other indexed repo. Omit for all."New value: +"Restrict to these source types. \"proposal\" is a Dev Fund grant request; \"github_item\" is an ordinary issue or PR from any other indexed repo; \"sdk_version\" is a released package version from the npm/Docker registries. Omit for all."
    • changedInput schema / properties / source_types / items / enum
      Previous value: -[
-  "cip",
-  "doc_page",
-  "forum_topic",
-  "mailing_message",
-  "proposal",
-  "github_item",
-  "whitepaper",
-  "blog_post",
-  "github_release",
-  "github_discussion",
-  "ecosystem_project",
-  "foundation_kb",
-  "youtube_video",
-  "gov_vote",
-  "radar_item",
-  "cip_attachment"
-]New value: +[
+  "cip",
+  "doc_page",
+  "forum_topic",
+  "mailing_message",
+  "proposal",
+  "github_item",
+  "whitepaper",
+  "blog_post",
+  "github_release",
+  "github_discussion",
+  "ecosystem_project",
+  "foundation_kb",
+  "youtube_video",
+  "gov_vote",
+  "radar_item",
+  "cip_attachment",
+  "sdk_version"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"How many chunks to return. Default 6, max 15. Capped at 2 per document so one long file cannot take every slot."
  3. Changed2 schema fields changed
    • changedInput schema / properties / source_types / description
      Previous value: -"Restrict to these source types. Omit for all."New value: +"Restrict to these source types. \"proposal\" is a Dev Fund grant request; \"github_item\" is an ordinary issue or PR from any other indexed repo. Omit for all."
    • changedInput schema / properties / source_types / items / enum
      Previous value: -[
-  "cip",
-  "doc_page",
-  "forum_topic",
-  "mailing_message",
-  "proposal",
-  "whitepaper",
-  "blog_post",
-  "github_release",
-  "github_discussion",
-  "ecosystem_project",
-  "foundation_kb",
-  "youtube_video",
-  "gov_vote",
-  "radar_item",
-  "cip_attachment"
-]New value: +[
+  "cip",
+  "doc_page",
+  "forum_topic",
+  "mailing_message",
+  "proposal",
+  "github_item",
+  "whitepaper",
+  "blog_post",
+  "github_release",
+  "github_discussion",
+  "ecosystem_project",
+  "foundation_kb",
+  "youtube_video",
+  "gov_vote",
+  "radar_item",
+  "cip_attachment"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / source_types / items / enum
      Previous value: -[
-  "cip",
-  "doc_page",
-  "forum_topic",
-  "mailing_message",
-  "proposal",
-  "whitepaper",
-  "blog_post",
-  "github_release",
-  "github_discussion",
-  "ecosystem_project",
-  "foundation_kb",
-  "youtube_video",
-  "gov_vote"
-]New value: +[
+  "cip",
+  "doc_page",
+  "forum_topic",
+  "mailing_message",
+  "proposal",
+  "whitepaper",
+  "blog_post",
+  "github_release",
+  "github_discussion",
+  "ecosystem_project",
+  "foundation_kb",
+  "youtube_video",
+  "gov_vote",
+  "radar_item",
+  "cip_attachment"
+]
  5. Changed1 schema field changed
    • changedInput schema / properties / source_types / items / enum
      Previous value: -[
-  "cip",
-  "doc_page",
-  "forum_topic",
-  "mailing_message",
-  "proposal",
-  "whitepaper",
-  "blog_post",
-  "github_release",
-  "github_discussion",
-  "ecosystem_project",
-  "foundation_kb",
-  "youtube_video"
-]New value: +[
+  "cip",
+  "doc_page",
+  "forum_topic",
+  "mailing_message",
+  "proposal",
+  "whitepaper",
+  "blog_post",
+  "github_release",
+  "github_discussion",
+  "ecosystem_project",
+  "foundation_kb",
+  "youtube_video",
+  "gov_vote"
+]
  6. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses concrete behavioral traits: the hybrid retrieval mechanism ('vector+FTS hybrid retrieval with reranking'), the corpus scope ('full Canton corpus'), and a specific result-limiting rule ('Capped at 2 per document'). These details add real value and align with the annotations.

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?

The description is dense yet front-loaded, starting with 'PRIMARY tool' and immediately clarifying scope. Every sentence adds critical guidance (usage, alternatives, workflow, result behavior) without redundancy, making it appropriately sized for the tool's importance.

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 complex search tool with no output schema, the description covers purpose, scope, retrieval method, limits, alternatives, and the downstream get_doc workflow. It is sufficiently complete for an agent to select and invoke it correctly.

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 already documents all parameters thoroughly (100% coverage), but the description enriches the limit parameter by explaining the 2-per-document cap and gives context for the query parameter via 'conceptual/meaning-based search.' This goes beyond a mere baseline of 3.

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?

The description clearly identifies semantic_search as the primary tool for open-ended how/why/what-is questions and troubleshooting, with a specific verb+resource ('conceptual/meaning-based search over the full Canton corpus'). It explicitly distinguishes itself from narrow curated tools like get_faq and find_known_issues, making its purpose unmistakable.

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?

Provides explicit usage guidance: 'Use this FIRST for anything a specific tool does not clearly own' and contrasts with alternatives by noting they 'cover only small hand-picked sets or need a literal error string.' It also gives a follow-up workflow ('call get_doc with a returned id'), covering both when and how to use it.

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