Skip to main content
Glama

canton-ccpedia

by io.github.UnityNodes
OverviewDiscussionsAdmin

list_mailing_threads

Read-onlyIdempotent

List threads from the Canton Network governance mailing lists (lists.sync.global groups: cip-discuss, cip-vote, cip-announce, 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

NameRequiredDescriptionDefault
groupNoRestrict to one of the 7 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.

  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 / group / description
      Previous value: -"Restrict to one of the 8 indexed groups."New value: +"Restrict to one of the 7 indexed groups."
    • changedInput schema / properties / group / enum
      Previous value: -[
-  "cip-discuss",
-  "cip-vote",
-  "cip-announce",
-  "globalSyncForum",
-  "grants-discuss",
-  "validator-announce",
-  "tokenomics-announce",
-  "supervalidator-announce"
-]New value: +[
+  "cip-discuss",
+  "cip-vote",
+  "cip-announce",
+  "grants-discuss",
+  "validator-announce",
+  "tokenomics-announce",
+  "supervalidator-announce"
+]
  3. 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"
+]
  4. 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."
  5. 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"
+]
  6. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds useful framing ('Returns thread metadata only', 'Canton-only', the channel identity) that tells the agent what the call yields and its scope.

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?

Four front-loaded sentences with no filler; the group enumeration and sibling disambiguation are the bulky parts but they earn their place. Slightly heavy on parenthetical detail.

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?

No output schema exists, and the description covers scope, filters, channel identity, and what it returns ('thread metadata only'). It does not describe return fields or paging behavior, but the schema's offset description carries paging, so it is nearly 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%, so all five parameters are already documented, and the description's 'filter by group, CIP number, or date' merely restates those dimensions. Baseline 3 applies because the schema carries the semantics.

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?

Specifies a concrete verb and resource ('List threads from the Canton Network governance mailing lists') and enumerates the indexed groups. It explicitly distinguishes the email channel from the web forum (get_discussion) and GitHub Discussions (list_github_discussions), so an agent can route correctly without opening another schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the two sibling channels it is not and the follow-up tool (get_mailing_thread) for message bodies, which is genuine routing guidance. However, it never contrasts itself against search_mailing_list, a sibling covering the same source, so the list-vs-search decision is left unstated.

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