Skip to main content
Glama

canton-ccpedia

by io.github.UnityNodes
OverviewDiscussionsAdmin

get_recent_deployments

Read-onlyIdempotent

Recent completed SV deployments/releases from sv_operations_calendar (operation_type in deploy|release|upgrade), cross-referenced with github_releases when the title names a SemVer-looking tag. Canton-specific. Use to answer "what shipped on MainNet recently?".

Input Schema

NameRequiredDescriptionDefault
limitNoHow many deployments to return, newest first. Default 10, max 50.
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
    • changedInput schema / properties / limit / description
      Previous value: -"Max rows (default 10)."New value: +"How many deployments to return, newest first. Default 10, max 50."
    • 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. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so safety is covered. The description adds real behavioral context beyond that: the data sources, the operation_type filter, and the conditional join with github_releases when a title looks like a SemVer tag. It does not describe result shape, but that is a minor omission for a list tool.

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 core resource and scope, then supporting detail; no filler sentences. Density is high and mildly jargon-heavy (sv_operations_calendar, SemVer-looking tag), but every clause carries information.

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?

For a two-optional-parameter read-only list tool with complete annotations and full schema coverage, the description supplies what the structured fields cannot: sources, filter values, and enrichment behavior. The only gap is that with no output schema, the returned fields are never characterized, though the schema notes the response echoes the offset.

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 description coverage is 100% and both parameters (limit, offset) are fully documented there, including default, max, paging behavior, and the echoed offset. The description adds nothing about these parameters, so the baseline 3 for schema-carried semantics is correct.

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 (recent completed SV deployments/releases), names the backing source (sv_operations_calendar), the filter (operation_type in deploy|release|upgrade), and an enrichment step (cross-reference with github_releases on SemVer-looking tags). Combined with the explicit 'Canton-specific' scoping, an agent can distinguish it from get_latest_release and search_release_notes without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The quoted question 'what shipped on MainNet recently?' gives an implied usage context, but there is no explicit when-not, no prerequisite, and no routing away from overlapping siblings such as get_latest_release, get_upcoming_operations, or search_release_notes.

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