Skip to main content
Glama

canton-ccpedia

by io.github.UnityNodes
OverviewDiscussionsAdmin

get_discussion

Read-onlyIdempotent

Get a single thread from the official Canton Network community forum (Discourse at forum-style discussions on ccpedia.xyz) by numeric topic id: title, category, view/post counts, and the first ~15 posts. Canton-only, served from CCPEDIA's cached forum index. This is the WEB FORUM. For GitHub Discussions use get_github_discussion, for sync.global mailing-list threads use get_mailing_thread. Get the id from search results or trending.

Input Schema

NameRequiredDescriptionDefault
idYesForum topic ID from a search result, e.g. 3242 or "topic:3242". Not a doc-page id: those go to get_doc.

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. Changed5 schema fields changed
    • addedInput schema / properties / id / anyOf
      Added value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  {
+    "type": "string"
+  }
+]
    • changedInput schema / properties / id / description
      Previous value: -"Forum topic ID"New value: +"Forum topic ID from a search result, e.g. 3242 or \"topic:3242\". Not a doc-page id: those go to get_doc."
    • removedInput schema / properties / id / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / id / minimum
      Removed value: --9007199254740991
    • removedInput schema / properties / id / type
      Removed value: -"integer"
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the safety profile is covered. The description adds genuinely new traits: results come from CCPEDIA's cached forum index (staleness implication), it is Canton-only, and only the first ~15 posts are returned. Pagination or a way to fetch further posts is not disclosed, which keeps this 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?

Purpose and returned fields are front-loaded ahead of the sibling routing and id-sourcing hints, so the shape is good. The parenthetical '(Discourse at forum-style discussions on ccpedia.xyz)' is garbled and mildly redundant with the opening clause, costing a point.

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 carries the burden and does enumerate the return fields and the ~15-post truncation and cache caveat. It omits how to retrieve posts beyond the first ~15 or whether the cached index lags live forum state, so it is strong but not fully 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 the single parameter already documents accepted forms (3242 or "topic:3242") and excludes doc-page ids. The description only lightly reinforces the id's origin ('search results or trending'), which the schema largely covers, so the baseline of 3 applies.

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 (get) and resource (a single forum thread) plus the exact source (Canton community forum, CCPEDIA cached index) and the fields returned (title, category, view/post counts, first ~15 posts). It is clearly distinguishable from sibling readers like get_github_discussion and get_mailing_thread.

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 routes among alternatives: 'For GitHub Discussions use get_github_discussion, for sync.global mailing-list threads use get_mailing_thread.' It also tells the agent where to obtain the required id ('from search results or trending'), leaving nothing to inference.

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