Skip to main content
Glama

Bryntum skill: bryntum-features

skill_bryntum_features
Read-onlyIdempotent

Find the built-in Bryntum feature for what the user is describing before writing a custom renderer, custom CSS, or a hand-drawn overlay, and the tier it needs. Use alongside the bryntum skill whenever a request is phrased as an outcome rather than an API — "shade 11:00-13:00 as lunch", "grey out weekends", "working hours are 9 to 5", "mark today", "draw arrows between tasks", "group by city", "a totals row", "a search box", "export to Excel", "print", "undo", "swimlanes", "baselines", "critical path", "recurring events", "split a task", "WIP limit", "highlight that row". Most of these are one config.

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

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that the result is markdown instructions and that it should precede custom implementation work, but says nothing about the returned payload's size or how the 'tier' information is presented. Useful context, but modest given the annotations carry most of the behavioral burden.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core instruction and the routing condition are front-loaded, which is good. However, the middle sentence is a ~20-item run-on list of quoted triggers that could be trimmed to a representative handful without losing the matching signal, making the description bulkier than its routing job requires.

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 parameterless skill-loader with no output schema, the description covers what it returns (markdown instructions), when to invoke it, and what it prevents (custom code for something built in). Only the handling of the returned instructions, such as their scope or length, is left unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the schema is empty and complete. Baseline for a no-parameter tool applies, with no added parameter meaning possible.

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 verb and resource: 'Find the built-in Bryntum feature ... and the tier it needs', and closes with the concrete output 'Returns the skill's instructions as markdown.' It also distinguishes itself from the complement `bryntum` skill and from the anti-pattern of hand-writing a custom renderer/CSS/overlay. Minor deduction because the opening frames the tool as a feature lookup when it actually loads skill instructions.

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 an explicit trigger condition ('whenever a request is phrased as an outcome rather than an API') and an explicit when-not ('before writing a custom renderer, custom CSS, or a hand-drawn overlay'). It names the sibling it should be used alongside (`bryntum`) and backs the routing rule with many concrete outcome phrasings.

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