Skip to main content
Glama

Bryntum skill: bryntum-styling

skill_bryntum_styling
Read-onlyIdempotent

Custom styling of Bryntum Scheduler event bars, any tier incl. the former Scheduler Pro (eventRenderer layouts, event bar DOM structure, padding CSS variables, sticky content) and widget rendition (built-in visual variants of buttons, text fields and tooltips, plus the form look). Use alongside the bryntum skill. Trigger on "eventRenderer", "style the event bars", "customize event content", "two-line events", "event bar padding", content not filling / overflowing the bar, "button style", "primary button", "filled button", "rendition", "outlined field", "form layout". For picking themes or dark mode use bryntum-theming instead.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, and the description is consistent with a pure lookup. It adds information the annotations do not: the tool returns the skill's instructions as markdown, and it is designed to be paired with the `bryntum` skill. It stops short of noting size or loading cost of the returned instructions, which would be the remaining useful detail.

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, then scope detail, then trigger phrases, then the exclusion — a sensible routing order. The quoted trigger list is long and somewhat keyword-stuffed, but each phrase serves as a distinct activation cue, so it mostly earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter skill-retrieval tool this covers everything an agent needs: what it covers, when to trigger it, which sibling to use instead, what the base skill pairing is, and that the return value is markdown instructions. No output schema is needed because the return type is stated inline.

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 description correctly says nothing about arguments, so there is no semantic gap to fill. Baseline 4 applies for a parameterless tool; no contradictions or phantom parameters are introduced.

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+resource: custom styling of Bryntum Scheduler event bars (eventRenderer layouts, CSS variables, sticky content) plus widget `rendition` variants and form look. It explicitly distinguishes itself from `skill_bryntum_theming` and points to the base `bryntum` skill, so an agent can separate it from all 13 siblings 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 Guidelines5/5

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

Gives both sides of the routing decision: use this for event bar styling and rendition/form look, use `bryntum-theming` instead for themes or dark mode, and it is meant to be combined with the `bryntum` skill. The long trigger-phrase list ('two-line events', 'primary button', 'outlined field') makes activation conditions concrete rather than inferable.

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