Skip to main content
Glama

canton-ccpedia

by io.github.UnityNodes

get_radar

Read-onlyIdempotent

Get the Canton Network Radar, CCPEDIA's curated feed of time-sensitive ecosystem alerts: breaking changes, upgrade deadlines, protocol migrations and required validator actions, each with deadline, affected components and source link. Filter by level (critical/important/ecosystem/all). Canton-only. Use when a user asks what's changing, what's about to break, or what deadlines are approaching on Canton.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
levelNoSeverity floor. "critical" and "important" return only that level; "ecosystem" is the low-severity feed; "all" (default) returns every live alert.all
limitNoHow many alerts to return, most severe and most recent first. Default 25.
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
    • addedInput schema / properties / level / description
      Added value: +"Severity floor. \"critical\" and \"important\" return only that level; \"ecosystem\" is the low-severity feed; \"all\" (default) returns every live alert."
    • 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"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 25,
+  "description": "How many alerts to return, most severe and most recent first. Default 25.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
  3. 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=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well-established. The description adds meaningful behavioral context by describing what each alert contains (deadline, affected components, source link), the severity levels, and that it is a curated feed. It doesn't go into pagination or output formatting, but this is not necessary given the simple read-only nature and full schema docs.

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 three sentences, front-loaded with the core purpose, and every sentence earns its place. It defines the resource, includes example alert types and output fields, states filtering capability, and explicitly maps to user intents. No fluff or 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?

This is a simple read-only list tool with no output schema, but the description covers the return contents (deadline, affected components, source link), filtering, and use cases. The schema fully documents all three parameters. Given the low complexity and rich schema annotations, the description is complete enough for an agent to select and invoke the tool correctly without ambiguity.

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?

The schema provides 100% coverage with detailed descriptions for each parameter: level explains the severity floor and enum values, limit describes default and max, offset describes paging behavior. The description only reiterates the level filter (critical/important/ecosystem/all) and adds the 'Canton-only' context, which is not a parameter-level semantic. Given the schema's strong documentation, the description adds marginal value beyond structured data, aligning with the baseline of 3.

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 clearly identifies the tool as getting the 'Canton Network Radar' with a specific verb ('Get') and a specific resource. It enumerates the content (time-sensitive ecosystem alerts: breaking changes, upgrade deadlines, protocol migrations, validator actions) and even lists included fields (deadline, affected components, source link). This distinguishes it from broadly similar siblings like get_breaking_changes or get_upcoming_deadlines by framing it as a curated, all-in-one feed.

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 the tool: 'Use when a user asks what's changing, what's about to break, or what deadlines are approaching on Canton.' It also clarifies scope ('Canton-only') and the filter level options. While it doesn't explicitly name alternatives, the intent mapping is so direct that an agent can confidently select it for those question types.

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