Skip to main content
Glama

canton-ccpedia

by io.github.UnityNodes
OverviewDiscussionsAdmin

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

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.

  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 / 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"
+}
  3. 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"
+}
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds behavior the annotations cannot: the feed is curated, live, time-sensitive, and each entry carries a deadline, affected components and a source link. It does not discuss freshness/caching or rate limits, but adds real value on top of the structured hints.

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?

Front-loaded with what the tool is, then content shape, then filter, then scope, then trigger. Three sentences, no filler, no repetition of schema 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?

With zero required params and no output schema, the description carries the return-shape burden and does so by naming deadline, affected components and source link, plus the level filter. Minor gap: it never distinguishes the radar entry from sibling feeds like get_breaking_changes or get_upcoming_deadlines, which is the one thing an agent would still need to choose 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 each parameter already carries a detailed description, including the nuanced severity-floor semantics of 'level'. The description only repeats the level enum; it says nothing about limit or offset paging that the schema does not already state. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (get the Canton Network Radar) and enumerates the content precisely: breaking changes, upgrade deadlines, protocol migrations, validator actions, each with deadline/components/source. The scope constraint 'Canton-only' is explicit. It stops short of distinguishing itself from overlapping siblings like get_breaking_changes or get_upcoming_deadlines, leaving the agent to infer that radar is the aggregated curated feed.

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?

Gives concrete trigger conditions: 'Use when a user asks what's changing, what's about to break, or what deadlines are approaching on Canton.' That is clear when-to-use guidance. There is no when-not guidance and no named alternative for narrower queries, so it falls short of the 5 anchor.

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