Skip to main content
Glama

Bryntum skill: bryntum-editor

skill_bryntum_editor
Read-onlyIdempotent

Customize Bryntum's built-in event/task editor popup (all products except Grid). Use alongside the bryntum skill to add, remove, or reorder editor fields and tabs, tweak validation, react to the editor opening/saving, or swap in a fully custom dialog. Trigger on phrases like "edit event popup", "task editor", "remove the % Complete field", "custom event editor", "eventEdit"/"taskEdit"/"basicTaskEdit" config, or "beforeEventEdit"/"beforeTaskEdit".

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/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 the one thing annotations can't convey: the return payload is 'the skill's instructions as markdown', which tells the agent to expect instructional text rather than data. It does not mention size, truncation, or how the returned guidance relates to the `bryntum` base skill's output.

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?

Front-loaded with the core verb and resource, then scope, then use cases, then triggers, then the return note. The long trigger-phrase list is dense but earns its place for routing; wording like 'for adding, removing, or reordering specific pieces' is mildly redundant with the earlier field/tab list.

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?

A zero-parameter, read-only retrieval tool needs subject scope, triggers, and return format, and this description supplies all three. No output schema exists, but the 'instructions as markdown' sentence covers what the caller would otherwise need explained.

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 input schema is empty (0 parameters, 100% coverage), so there is no parameter semantics to explain and the baseline is 4. The description correctly implies a zero-argument invocation by describing the tool purely in terms of subject matter.

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 and resource ('Customize Bryntum's built-in event/task editor popup') and adds a scoping constraint ('all products except Grid') that separates it from the Grid-focused siblings. An agent can identify this as the editor-customization skill without reading any other definition.

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?

Enumerates concrete use cases (add/remove/reorder fields and tabs, tweak validation, react to open/save, swap in a custom dialog) and trigger phrases plus config names ('eventEdit', 'beforeTaskEdit'), which is strong routing guidance. It also names the companion skill ('bryntum') but never says which sibling to choose instead when the work falls outside the popup, so it stops short of full when-not coverage.

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