Skip to main content
Glama

Bryntum skill: bryntum-vanilla

skill_bryntum_vanilla
Read-onlyIdempotent

Vanilla JS patterns for Bryntum components. Use this alongside the bryntum skill when building or integrating any Bryntum product (Scheduler, Scheduler Pro, Gantt, Calendar, Grid, TaskBoard) without a framework — plain JavaScript or TypeScript with no React/Angular/Vue, on the 8.0 tier packages (@bryntum/<product>-<tier>) or on 7.x. Trigger when there is no framework in package.json or when the user asks about vanilla JS Bryntum integration or direct class instantiation.

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_vanilla"
  }
}

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds value beyond that by disclosing the return format ('instructions as markdown') and the package-version applicability, though it says nothing about length, caching, or whether the content is product-specific or generic.

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 product scope are front-loaded, followed by the trigger conditions and return format; nothing is repeated from the title. The trigger sentence is dense with product names and version tiers but each clause carries routing information an agent would otherwise have to guess.

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-argument skill-retrieval tool with no output schema, the description covers what it returns, when to use it, which companion skill to pair it with, and which versions it applies to. Only minor gaps remain, such as whether the markdown content is product-agnostic or requires specifying a product elsewhere.

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 and the schema is an empty object, so there is no parameter semantics to explain; the baseline for a no-param tool applies. The description correctly avoids inventing inputs the schema does not have.

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 names the specific resource (vanilla JS patterns for Bryntum components) and the exact scope of products covered, then states the return behavior: 'Returns the skill's instructions as markdown.' It explicitly contrasts with framework variants by saying 'no React/Angular/Vue', which lets an agent distinguish it from skill_bryntum_react, skill_bryntum_angular, and skill_bryntum_vue 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?

It gives concrete trigger conditions: 'no framework in package.json', a user question about vanilla JS integration, or direct class instantiation. It also names the companion skill to load alongside it (`bryntum`) and the package/version tiers (8.0 `@bryntum/<product>-<tier>` or 7.x), which is the routing information an agent needs.

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