Skip to main content
Glama

Bryntum skill: bryntum-migrate

skill_bryntum_migrate
Read-onlyIdempotent

Upgrade an existing Bryntum app (Gantt, Scheduler Pro, Scheduler, Calendar, Grid, TaskBoard) to a newer Bryntum version — 6.x → 7.x, 7.x → 7.y, 7.x → 8.x, 8.x → 8.y (including the 8.0 tier package rename, such as @bryntum/grid → @bryntum/grid-enterprise, Scheduler Pro → @bryntum/scheduler-enterprise, and the 8.0.1 Business → Core tier rename, @bryntum/grid-business → @bryntum/grid-core). Gathers the upgrade guides and changelogs for every release crossed, across the product and the products it inherits from, checks them against the app's code, writes a migration plan for approval, then applies and verifies it. Use for "upgrade / update / migrate Bryntum to a newer version", "bump @bryntum/*", "what changed between 6.x and 7.x", "my Gantt/Scheduler broke after updating", or the error "CSS version X doesn't match bundle version Y". Not for migrating from another vendor (DHTMLX, Syncfusion, FullCalendar, …) or first-time installation (use the bryntum skill).

Returns the skill's instructions as markdown.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "skill_bryntum_migrate"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real context beyond them: it describes the internal workflow (gather guides and changelogs across inherited products, check against app code, write a plan for approval, apply and verify) and closes with 'Returns the skill's instructions as markdown.' The phrase 'applies and verifies it' describes the skill's instructed workflow rather than the tool's own side effects, which is slightly ambiguous next to readOnlyHint=true, but the final sentence disambiguates that the call itself only returns instructions.

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?

Purpose and version scope are front-loaded, then triggers, then exclusions, then the return format — a sensible order with no filler sentences. The parenthetical catalogue of 8.0 package renames is dense but each name earns its place as a retrieval trigger; it is the main reason this is a 4 rather than a 5.

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 parameters, no output schema, and annotations already covering the safety profile, the description supplies scope, version boundaries, triggers, exclusions, and the return format. The only residual gap is that it does not say how the returned markdown should be consumed (e.g., that the agent should follow it as a multi-step procedure), which matters for a workflow-delivering skill tool.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. Nothing in the text misleads about inputs.

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 ('Upgrade an existing Bryntum app') and enumerates the supported products and version paths (6.x→7.x, 7.x→8.x, tier package renames). It also names what it is not — not a cross-vendor migration and not first-time installation — so an agent can distinguish it from skill_bryntum and skill_bryntum_from_extjs without opening any schema.

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?

Gives explicit when-to-use triggers in quoted user phrasing ('bump @bryntum/*', 'my Gantt/Scheduler broke after updating') plus a concrete error string, and explicit exclusions that route the agent elsewhere ('first-time installation (use the `bryntum` skill)'). Both the positive and negative cases are covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources