Skip to main content
Glama

Bryntum skill: bryntum-react

skill_bryntum_react
Read-onlyIdempotent

React-specific patterns for Bryntum components. Use this alongside the bryntum skill when building or integrating any Bryntum product (Scheduler, Scheduler Pro, Gantt, Calendar, Grid, TaskBoard) in a React project, on the 8.0 tier packages (@bryntum/<product>-react-<tier>) or on 7.x. Trigger when the project has React in package.json or when the user asks about React + Bryntum integration, JSX config, StrictMode issues, or @bryntum/*-react packages.

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

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=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds meaningful context beyond that: the content scope (React patterns, tiers 8.0 `@bryntum/<product>-react-<tier>` and 7.x) and the return format (markdown instructions). It does not state the approximate size or structure of the returned instructions, which keeps it short of a 5.

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 list are front-loaded, and the trigger conditions follow in a single dense sentence. The version/tier detail (`@bryntum/<product>-react-<tier>`, 7.x) is useful but slightly heavy for a retrieval skill, keeping it just below maximal conciseness.

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, read-only skill-retrieval tool with no output schema, the description supplies what an agent needs: when to select it, what content it covers, what it returns, and which sibling to pair it with. It stops short of describing how the markdown is organized or whether it should be read before or after the `bryntum` skill.

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; the baseline for a parameterless tool applies. Nothing in the description misleads about inputs, and it correctly implies the call is a plain retrieval with no arguments.

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 a specific resource (React-specific patterns for Bryntum components) and enumerates the covered products, then states the output form ('Returns the skill's instructions as markdown'). It is clearly separable from siblings like skill_bryntum_angular, skill_bryntum_vue, and skill_bryntum_vanilla by the React framing.

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 explicit trigger conditions: React present in package.json, or the user asking about React + Bryntum integration, JSX config, StrictMode issues, or @bryntum/*-react packages. It also routes the agent to the right combination ('use this alongside the `bryntum` skill'), which is the key alternative relationship among the siblings.

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