canton-ccpedia

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

Name	Required	Description
`limit`	No	How many chunks to return. Default 6, max 15. Capped at 2 per document so one long file cannot take every slot.
`query`	Yes	Free-form question or phrase.
`source_types`	No	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; "dev_fund_comment" is a comment, review or inline review comment on a Dev Fund PR; "dev_fund_file" is a proposal file. Omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 21, 2026

changedInput schema / $schema

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

Changed2 schema fields changedOct 11, 2026

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; \"sdk_version\" is a released package version from the npm/Docker registries. 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; \"dev_fund_comment\" is a comment, review or inline review comment on a Dev Fund PR; \"dev_fund_file\" is a proposal file. 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",
-  "sdk_version"
-]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",
+  "dev_fund_comment",
+  "dev_fund_file"
+]

Changed2 schema fields changedAug 9, 2026

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"
+]

Changed1 schema field changedAug 5, 2026

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."

Changed2 schema fields changedAug 4, 2026

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"
+]

Changed1 schema field changedJul 27, 2026

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"
+]

Changed1 schema field changedJul 27, 2026

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"
+]

First observedJul 20, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real context beyond them — the hybrid vector+FTS retrieval with reranking, the Canton-scoped corpus, and the two-step retrieval-then-read workflow. It stops short of stating return shape (scores/ids) or latency/rate behavior, keeping it from a 5.

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 dense and slightly long, with heavy parenthetical corpus and sibling lists, but it is well front-loaded — the primary use case comes first, then scope, then routing. Nearly every clause carries routing or scope value, so little is wasted.

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 still hands the agent the essential next step (follow up with get_doc using a returned id) and defines the corpus and retrieval method. The only omission is the exact return shape, which keeps it just under complete.

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% and every parameter (query, limit, source_types) is already documented in the schema, including the enum values and the per-document cap. The description adds no syntax or format detail beyond what the schema provides, so the baseline of 3 is appropriate.

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 names a specific verb+resource (conceptual semantic search) and states its scope precisely: open-ended how/why/what-is questions, symptom troubleshooting, and config/setup lookup over a named corpus. It explicitly distinguishes itself as the PRIMARY tool and contrasts its breadth against narrower siblings, so an agent can tell it apart without opening any schema.

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?

It gives explicit when-to-use ('open-ended questions', 'anything a specific tool does not clearly own'), names the alternatives it supersedes (get_faq, find_known_issues, diagnose_error) with the reason each is limited (hand-picked sets, need a literal error string), and closes the loop with a follow-up action (call get_doc with a returned id). This is a full routing decision, not an implied one.

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

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

semantic_search

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources