Skip to main content
Glama

canton-ccpedia

by io.github.UnityNodes
OverviewDiscussionsAdmin

list_cips

Read-onlyIdempotent

Browse Canton Improvement Proposals (CIPs), optionally filtered by status (Draft, Early Draft, In Review, Proposed, Proposed Amendment, 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

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.

  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",
-  "Pending",
-  "Review",
-  "Superseded",
-  "all"
-]New value: +[
+  "Draft",
+  "Early Draft",
+  "In Review",
+  "Proposed",
+  "Proposed Amendment",
+  "Approved",
+  "Active",
+  "Final",
+  "Withdrawn",
+  "Rejected",
+  "Replaced",
+  "Obsolete",
+  "Pending",
+  "Review",
+  "Superseded",
+  "all"
+]
  2. 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"
  3. 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"
+]
  4. 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."
  5. 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"
+}
  6. 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"
+]
  7. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, non-open-world operation, so the description's added value is the return-shape warning: 'Returns a metadata list (id, title, status, type, author). Not full text.' That prevents a common failure mode (expecting full proposal text). Pagination behavior is covered by the schema but not echoed here, which keeps it just below 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?

Front-loaded with the action and filters, then the return shape, then routing/exclusions — a logical order with no filler. The 13-value status enumeration is partly redundant with the enum and slightly bloats the definition, though it does aid fast scanning.

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?

With no output schema, the description carries return-value information and does so adequately: it names the metadata fields returned, states the full text is not included, and covers paging indirectly via the schema. Scope limits and the sibling alternative are both present, so an agent can call this correctly without further context.

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 75% and both limit/offset are documented in-schema with paging semantics, so baseline is 3. The description adds the status vocabulary inline, but its list omits schema enum values 'Review', 'Superseded', and 'all', making it slightly lossy rather than additive; the type filter gets only a repeated example.

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 ('Browse Canton Improvement Proposals (CIPs)') plus the filter dimensions. It explicitly scopes to Canton/Daml/Splice and disclaims other 'CIP' schemes, so the agent can tell it apart from get_cip and from unrelated proposal tooling.

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 says when to use it ('discover or enumerate CIPs when you don't have a specific ID') and names the alternative ('use get_cip to read one'). It also adds a hard exclusion ('Canton/Daml/Splice governance only. Not Cardano or other CIP schemes'), which is exactly the routing information an agent needs.

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