Skip to main content
Glama

canton-ccpedia

by io.github.UnityNodes
OverviewDiscussionsAdmin

get_mailing_thread

Read-onlyIdempotent

Get every message (oldest first) in a specific Canton Network governance mailing-list thread on lists.sync.global (cip-discuss, cip-vote, grants-discuss, etc.). Canton-only. Pass the thread id from list_mailing_threads. This is the email/mailing-list channel. Not the web forum (get_discussion) or GitHub Discussions.

Input Schema

NameRequiredDescriptionDefault
idYesThread id exactly as list_mailing_threads prints it. Both forms work: a numeric archive topic id ("119286914") and a message id for messages the archive never threaded ("cip-discuss-809").
limitNoHow many messages (oldest first) to return. Default 25, max 100. The header states the full held count and the range shown.
offsetNoSkip this many messages before returning, for paging through a long thread.

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
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 25,
+  "description": "How many messages (oldest first) to return. Default 25, max 100. The header states the full held count and the range shown.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Skip this many messages before returning, for paging through a long thread.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Thread id, e.g. \"cip-discuss-12345\"."New value: +"Thread id exactly as list_mailing_threads prints it. Both forms work: a numeric archive topic id (\"119286914\") and a message id for messages the archive never threaded (\"cip-discuss-809\")."
  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, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value beyond that: deterministic oldest-first ordering and the Canton-only/lists.sync.global scope restriction. It does not discuss paging behavior, but that is documented in the schema instead.

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?

Four short sentences with no waste; the scope/ordering constraint is front-loaded and the routing exclusions come last. Nothing is repeated or padded.

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 list tool with a fully documented 3-parameter schema and no output schema, the description covers what it returns (all messages, oldest first), the source channel, and the id source. An agent has everything needed to 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 coverage is 100% and the id parameter documentation already explains both accepted id forms in depth, so the schema carries the load. The description adds only the provenance hint that the id comes from list_mailing_threads; limit/offset get no description-level elaboration. Baseline 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?

States a specific verb and resource ("Get every message ... in a specific Canton Network governance mailing-list thread on lists.sync.global"), names the concrete channel (cip-discuss, cip-vote, grants-discuss) and explicitly excludes the web forum and GitHub Discussions siblings. An agent can distinguish it from get_discussion / get_github_discussion 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?

Gives the prerequisite for the id ("Pass the thread id from list_mailing_threads") and names both alternatives it is not ("Not the web forum (get_discussion) or GitHub Discussions"). Both the when and the when-not are stated explicitly.

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