Skip to main content
Glama
vuluu2k

sbuilder-mcp

by vuluu2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sb_set

Set style, config, or specials keys on a single node or multiple via edits, with breakpoint-specific overrides. Use base:true for fallback values, state for interaction states, and unset to remove keys.

Instructions

Write style, config or specials keys on one node, or on many through edits (one save, one live frame). Per BREAKPOINT by default; base:true writes the fallback layer, right for a value that should not vary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
baseNo
keysNo
editsNo
forceNoOverride a render-inference guard; reported as forced
stateNoAn interaction state — "hover", or "stuck" for how a pinned element looks once it is stuck (needs a sticky/fixed self-or-ancestor; a descendant styles itself through the host).
unsetNoKeys to REMOVE from the same slot — the only way to undo a write. Setting null is not the same: null is a stored value, so the override still counts as present.
dry_runNo
namespaceNo
breakpointNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.63.0
    • addedInput schema / properties / force
      Added value: +{
+  "description": "Override a render-inference guard; reported as forced",
+  "type": "boolean"
+}
  2. Changed3 schema fields changedv0.12.0
    • addedInput schema / properties / edits / items / properties / unset
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedInput schema / properties / state / description
      Previous value: -"An interaction state, e.g. \"hover\""New value: +"An interaction state — \"hover\", or \"stuck\" for how a pinned element looks once it is stuck (needs a sticky/fixed self-or-ancestor; a descendant styles itself through the host)."
    • addedInput schema / properties / unset
      Added value: +{
+  "description": "Keys to REMOVE from the same slot — the only way to undo a write. Setting null is not the same: null is a stored value, so the override still counts as present.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  3. First observedv0.1.4

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only mark the tool as non-read-only and non-destructive, so the description carries the burden of explaining actual behavior. It adds meaningful detail: edits apply in one save/live frame, breakpoint is the default scope, and base:true targets the fallback layer. It does not discuss side effects like unset or force, but it does not contradict the annotations either.

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

Conciseness5/5

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

The description is only two sentences, front-loaded with the core operation and with no filler. The second sentence adds genuinely important base/breakpoint guidance rather than restating the schema.

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

Completeness3/5

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

Given 10 parameters, nested edit objects, and no output schema, the description alone is not complete: it does not explain how a node is identified, what state and unset mean, or what edits require structurally. The schema fills many gaps, but the prose still leaves important selection and invocation questions open.

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?

Schema description coverage is only 30%, so the description needs to compensate, and it does add meaning for base, breakpoint, namespace, and edits. However, it leaves id, state, unset, force, and dry_run unexplained in prose, relying on the schema to carry those details.

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?

The description names a specific operation — 'Write style, config or specials keys' — and clearly scopes it to one node or many through edits. This distinguishes it from sibling mutation tools like sb_add or sb_remove, and the base:true clarification removes ambiguity about which layer gets written.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description provides useful context such as 'Per BREAKPOINT by default' and using base:true for values that should not vary, which implies when certain parameters matter. However, it never explicitly says when to use sb_set versus an alternative, nor does it mention when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools