Skip to main content
Glama

canton-ccpedia

by io.github.UnityNodes

list_mailing_threads

Read-onlyIdempotent

List threads from the Canton Network governance mailing lists (lists.sync.global groups: cip-discuss, cip-vote, cip-announce, globalSyncForum, grants-discuss, validator-announce, tokenomics-announce, supervalidator-announce). Filter by group, CIP number, or date. Canton-only. This is the EMAIL/mailing-list channel. Distinct from the web forum (get_discussion) and GitHub Discussions (list_github_discussions). Returns thread metadata only; use get_mailing_thread for message bodies.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupNoRestrict to one of the 8 indexed groups.
limitNoHow many threads to return. Default 20, max 100.
sinceNoEarliest last_post_at ISO date.
cip_idNoCIP number filter, e.g. "0117". Returns only threads tagged with this CIP.
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 / group / description
      Previous value: -"Restrict to one of the eight indexed groups."New value: +"Restrict to one of the 8 indexed groups."
    • changedInput schema / properties / group / enum
      Previous value: -[
-  "cip-discuss",
-  "cip-vote",
-  "cip-announce",
-  "globalSyncForum",
-  "grants-discuss",
-  "validator-announce",
-  "supervalidator-announce",
-  "tokenomics-announce"
-]New value: +[
+  "cip-discuss",
+  "cip-vote",
+  "cip-announce",
+  "globalSyncForum",
+  "grants-discuss",
+  "validator-announce",
+  "tokenomics-announce",
+  "supervalidator-announce"
+]
  2. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"How many threads to return. Default 20, max 100."
    • addedInput schema / properties / offset / description
      Added value: +"Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used."
  3. Changed2 schema fields changed
    • changedInput schema / properties / group / description
      Previous value: -"Restrict to one of the six indexed groups."New value: +"Restrict to one of the eight indexed groups."
    • changedInput schema / properties / group / enum
      Previous value: -[
-  "cip-discuss",
-  "cip-vote",
-  "cip-announce",
-  "globalSyncForum",
-  "grants-discuss",
-  "validator-announce"
-]New value: +[
+  "cip-discuss",
+  "cip-vote",
+  "cip-announce",
+  "globalSyncForum",
+  "grants-discuss",
+  "validator-announce",
+  "supervalidator-announce",
+  "tokenomics-announce"
+]
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful behavioral scope: Canton-only, email/mailing-list channel, and 'Returns thread metadata only; use get_mailing_thread for message bodies.' This goes beyond the annotations without contradicting them.

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 but efficient: it names the exact groups, states the filtering dimensions, flags Canton-only scope, distinguishes channels, and routes body retrieval. Every sentence carries decision-relevant information, and the key boundary is stated up front.

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 read-only listing tool with no output schema, the description is complete enough: it defines the source, scope, filtering options, return boundary, and the sibling tool for bodies. Combined with fully described parameters, an agent can select and invoke it correctly.

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%, with default values, bounds, enum options, and a cip_id example already documented. The description adds a compact prose summary of 'Filter by group, CIP number, or date' but does not substantially enrich the parameter semantics beyond what the schema provides.

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 opens with a specific verb and resource: 'List threads from the Canton Network governance mailing lists', and enumerates the exact groups. It explicitly distinguishes itself from the web forum, GitHub Discussions, and get_mailing_thread, so there is no ambiguity about what this tool does.

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?

The description names the alternative channels and sibling tools: get_discussion for the web forum, list_github_discussions for GitHub Discussions, and get_mailing_thread for message bodies. It also states the filter dimensions, making when to use this tool and when to switch clear.

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