Skip to main content
Glama

canton-ccpedia

by io.github.UnityNodes

list_cips

Read-onlyIdempotent

Browse Canton Improvement Proposals (CIPs), optionally filtered by status (Draft, Early Draft, In Review, Proposed, Approved, Active, Final, Withdrawn, Rejected, Replaced, Obsolete, Pending) and type (e.g. "Standards Track"). Returns a metadata list (id, title, status, type, author). Not full text. Use to discover or enumerate CIPs when you don't have a specific ID; use get_cip to read one. Canton/Daml/Splice governance only. Not Cardano or other 'CIP' schemes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoType filter, e.g. "Standards Track"
limitNoHow many CIPs to return. Default 20, max 100. The response states the full count, which can exceed this limit; page with offset.
offsetNoSkip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.
statusNoall

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / properties / status / enum
      Previous value: -[
-  "Draft",
-  "Early Draft",
-  "In Review",
-  "Proposed",
-  "Approved",
-  "Active",
-  "Final",
-  "Withdrawn",
-  "Rejected",
-  "Replaced",
-  "Obsolete",
-  "Review",
-  "Superseded",
-  "all"
-]New value: +[
+  "Draft",
+  "Early Draft",
+  "In Review",
+  "Proposed",
+  "Approved",
+  "Active",
+  "Final",
+  "Withdrawn",
+  "Rejected",
+  "Replaced",
+  "Obsolete",
+  "Pending",
+  "Review",
+  "Superseded",
+  "all"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"How many CIPs to return. Default 20, max 100. The response states the full count; there are 124, so the maximum does not reach all of them."New value: +"How many CIPs to return. Default 20, max 100. The response states the full count, which can exceed this limit; page with offset."
  3. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"How many CIPs to return. Default 20, max 100. The response states the full count; there are 124, so the maximum does not reach all of them."
    • 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. Changed1 schema field changed
    • changedInput schema / properties / status / enum
      Previous value: -[
-  "Draft",
-  "Review",
-  "Final",
-  "Withdrawn",
-  "Rejected",
-  "Superseded",
-  "all"
-]New value: +[
+  "Draft",
+  "Early Draft",
+  "In Review",
+  "Proposed",
+  "Approved",
+  "Active",
+  "Final",
+  "Withdrawn",
+  "Rejected",
+  "Replaced",
+  "Obsolete",
+  "Review",
+  "Superseded",
+  "all"
+]
  5. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, and non-destructive behavior. The description adds valuable behavioral context by clarifying that only a metadata list is returned, not full proposal text, and that filters further narrow results. It does not contradict the annotations.

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?

The description is well-structured and front-loads the core action, output shape, and usage guidance. The status enumeration is somewhat lengthy but provides value beyond the schema's bare enum. Overall, each sentence earns its place with minimal redundancy.

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?

There is no output schema, so the description correctly explains the return shape ('metadata list (id, title, status, type, author)'). It also covers when to use the tool, what it does not return, and domain boundaries. Pagination details are already in the input schema, so nothing essential is missing.

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?

With 75% schema description coverage, the schema already documents limit and offset thoroughly. The description adds meaning by enumerating many allowed statuses and giving a type example, compensating for the status parameter's enum-only schema representation. It does not duplicate the schema's detailed pagination 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?

The description states a specific verb ('Browse') and resource ('Canton Improvement Proposals'), enumerates the filtering dimensions (status, type), and explicitly distinguishes itself from get_cip by noting it returns only metadata, not full text. This is unambiguous and immediately differentiates it from siblings.

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 explicitly states when to use this tool ('when you don't have a specific ID'), names the alternative ('use get_cip to read one'), and warns against domain confusion ('Canton/Daml/Splice governance only. Not Cardano or other CIP schemes'). This leaves no ambiguity about selection.

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