Skip to main content
Glama

Bryntum skill: bryntum-drag-and-drop

skill_bryntum_drag_and_drop
Read-onlyIdempotent

Drag-and-drop INTO a Bryntum Scheduler (any tier, incl. the former Scheduler Pro) / Gantt from an outside source — a sidebar of unscheduled jobs, plain s, a third-party grid (AG Grid), or a Bryntum Grid. Use alongside the bryntum skill whenever items are dragged onto the timeline. Trigger on phrases like "drag from sidebar", "drag unscheduled tasks", "drag onto the scheduler", "external drag source", "DragHelper", or a drop being "rejected"/"not working".

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

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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the return contract ("Returns the skill's instructions as markdown"), which matters because no output schema exists; it does not discuss size or freshness of the returned instructions, a minor remaining gap.

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?

Scope is front-loaded, followed by routing triggers and the return format, with no filler sentences. The trigger-phrase inventory is slightly long and partially overlaps the scoping sentence, but each phrase aids skill routing.

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 with no output schema, the description covers the triggering scenario, the companion skill to combine with, and the shape of the return value. Nothing an agent needs in order to select and invoke it correctly is missing.

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 the baseline is 4; there is no parameter meaning to convey beyond the schema. The description correctly implies a no-argument invocation by describing only scenario-based routing.

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 scenario with verb and target: dragging items INTO a Bryntum Scheduler/Gantt from an outside source, and enumerates source types (sidebar, plain divs, AG Grid, Bryntum Grid). This is clearly differentiated from sibling skills such as skill_bryntum, skill_bryntum_angular, or skill_bryntum_crud 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?

Explicitly instructs to use it alongside the `bryntum` skill whenever items are dragged onto the timeline, and lists concrete trigger phrases ("drag from sidebar", "external drag source", "DragHelper", drops being "rejected"/"not working"). The "INTO ... from an outside source" scoping implicitly excludes internal reordering, leaving little to inference.

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