Skip to main content
Glama

canton-ccpedia

by io.github.UnityNodes
OverviewDiscussionsAdmin

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

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.

  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
    • 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"
+]
  3. 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"
+}
  4. 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"
  5. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover the read-only, non-destructive, idempotent, closed-world safety profile. The description adds important behavioral context beyond those annotations, especially the forum coverage limitation (topic title and first post only) and the fallback to semantic_search for forum replies. It does not document rate limits or response shape, but no output schema exists and the caveat is the main behavioral risk.

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 front-loaded with scope and exclusions, then routes to alternatives and ends with the important forum caveat. Every sentence adds actionable information: no repetition or filler.

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 search tool with full schema coverage, clear annotations, and no output schema, the description supplies everything an agent needs: coverage scope, exclusions, alternative routing, and the key indexing limitation for forum content.

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?

Schema coverage is 100%, so the baseline is 3. The description still adds meaning by listing the covered source types and clarifying that 'forum' matches are limited to topic titles and first posts, which directly affects interpretation of the type parameter and search results.

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 states a specific verb and resource: keyword/full-text search over the Canton Network knowledge base, with an explicit list of covered source types. It also distinguishes itself from semantic_search and get_doc, so an agent can identify the correct tool without opening sibling 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?

It gives explicit when-to-use guidance: exact-term/name lookups here, conceptual questions via semantic_search, and full-page reading via get_doc once an id is known. It also states clear exclusions: not for other blockchains, the web, or local files.

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