Skip to main content
Glama

Bryntum skill: bryntum-crud

skill_bryntum_crud
Read-onlyIdempotent

Backend, CrudManager, and AjaxStore patterns for Bryntum components. Use this alongside the bryntum skill when the user needs to connect a Bryntum product to a backend — loading data from an API, persisting changes, or setting up sync. Trigger on phrases like "connect to a backend", "save data", "load from server", "CrudManager", "project transport", "AjaxStore", "sync", "REST API", or "database" in a Bryntum project context.

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

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 structurally. The description adds that the return value is the skill's instructions in markdown, which is genuinely useful context beyond the annotations, but says nothing about output size, whether content is static, or how much of the skill is returned.

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?

The purpose and companion-skill guidance are front-loaded in the first sentence, and the return-format note is a single closing line with no waste. The trigger-phrase enumeration is somewhat long but serves a real activation purpose for a skill-routing tool.

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 skill-loading tool with no output schema, the definition covers what it contains, when to invoke it, and what form the response takes. The only minor gap is that it does not mention sibling skills in the same family (e.g. framework-specific ones) that might also need loading.

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 meaning to convey and the baseline of 4 applies. The description does not introduce any spurious call-argument concepts.

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 names the specific subject matter (backend, CrudManager, and AjaxStore patterns) and states the concrete deliverable: 'Returns the skill's instructions as markdown.' That distinguishes it from the generic `bryntum` skill, though the differentiation is stated as a companion relationship rather than an explicit contrast with siblings like search_bryntum_docs.

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?

It gives clear activation conditions ('use alongside the `bryntum` skill when the user needs to connect a Bryntum product to a backend') plus a concrete list of trigger phrases covering load, save, and sync scenarios. It does not say when to prefer search_bryntum_docs or the framework-specific skills over this one, so there is no explicit exclusion guidance.

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