Skip to main content
Glama

Bryntum skill: bryntum

skill_bryntum
Read-onlyIdempotent

Build and integrate Bryntum components — Scheduler, Scheduler Pro, Gantt, Calendar, Grid, TaskBoard — even when "Bryntum" isn't mentioned by name. Covers the 8.0 tier packages (@bryntum/<product>-<tier>), license keys and trials, and 7.x apps. Trigger on phrases like "add a scheduler", "gantt chart", "grid component", "calendar view", "task board", "resource scheduling", any mention of @bryntum/* npm packages, or questions about Bryntum tiers, license keys, CSS imports, themes, or framework wrappers (Angular, React, Vue). When in doubt, use this 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"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered elsewhere. The description adds only the return shape ('Returns the skill's instructions as markdown'), which is useful but thin, and says nothing about size, cost, or ordering relative to the specialized skills.

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 is front-loaded in the first clause, followed by coverage, then triggers, then the return value; no sentence is filler. The trigger enumeration is long but each phrase adds a distinct entry point, so it earns its length.

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 zero-parameter skill loader with no output schema, the description covers what the tool does, when to trigger it, and what it returns. What is missing is guidance on how this umbrella relates to the twelve sibling skills, which matters given the crowded namespace.

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 zero parameters, so there is no parameter semantics to document and the baseline applies. The description correctly implies a parameterless invocation by describing the tool purely as a skill lookup.

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?

The description states a specific action (build and integrate components) and enumerates the concrete resources covered: Scheduler, Scheduler Pro, Gantt, Calendar, Grid, TaskBoard, plus 8.0 tier packages and 7.x apps. It is clearly distinct in scope from a docs search, but it overlaps the specialized siblings (skill_bryntum_react, skill_bryntum_theming, etc.) without saying how it differs from them.

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?

It gives explicit when-to-use guidance via a long trigger list plus the strong fallback 'When in doubt, use this skill', and notably says to fire even when 'Bryntum' isn't named. It offers no when-not guidance and never routes to the more specific sibling skills, which is the main gap for an umbrella skill.

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