Skip to main content
Glama

sb_add

Build complete page sections by adding a component or nested subtree under a parent in one call. Pass children to construct multi-node blocks instead of adding nodes one at a time.

Instructions

Add an element — or a whole NESTED subtree — under a parent. One call builds a complete section: pass children rather than calling this once per node.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "parent_id": "<parent_id>",
      "spec": "<spec>"
    },
    "name": "sb_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
specYes
forceNoOverride a render-inference guard; reported as forced
indexNo
dry_runNo
parent_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.98.3
    • addedInput schema / properties / spec / properties / responsive
      Added value: +{
      +  "additionalProperties": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "config": {
      +        "additionalProperties": {},
      +        "type": "object"
      +      },
      +      "style": {
      +        "additionalProperties": {},
      +        "type": "object"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "propertyNames": {
      +    "enum": [
      +      "desktop",
      +      "laptop",
      +      "tablet",
      +      "mobile"
      +    ]
      +  },
      +  "type": "object"
      +}
  2. Changed1 schema field changedv0.63.0
    • addedInput schema / properties / force
      Added value: +{
      +  "description": "Override a render-inference guard; reported as forced",
      +  "type": "boolean"
      +}
  3. First observedv0.1.4

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this a non-read, non-destructive mutation, so the safety profile is covered. The description usefully discloses the recursive nesting behavior, but it omits the existence of a 'render-inference guard' (only hinted at in the schema's force param), says nothing about what happens on failure or partial subtree insertion, and never mentions dry_run's purpose — noticeable gaps for a mutating tree operation.

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?

Two short sentences, zero filler, with the core capability (nested subtree in one call) front-loaded ahead of the efficiency instruction. Everything present earns its place.

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

Completeness2/5

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

This is a mutating tool with a deeply nested spec object, five parameters at 20% schema coverage, and no output schema — so the description should say what the call returns (e.g., created node id) and how index/force/dry_run behave. It covers the recursive spec shape but leaves the agent without enough to call it correctly for positional inserts or guarded overrides.

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

Parameters2/5

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

Schema description coverage is only 20%, so the description must compensate and largely does not: index (insertion position), dry_run, and parent_id semantics are unexplained, and 'force' carries only the cryptic schema note about a render-inference guard. The only value added is the hint that spec.children holds nested specs rather than requiring repeated calls.

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?

States a specific verb (add) and resource (an element or nested subtree under a parent), and the 'one call builds a complete section' framing clarifies the recursive/batch nature that a naive reader would miss. It does not name which sibling to use instead (sb_move, sb_set, sb_duplicate), so differentiation is implicit rather than explicit.

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?

Gives one real usage rule — 'pass children rather than calling this once per node' — which tells the agent how to batch efficiently. But there is no statement of preconditions (must a page be open? does the parent have to exist?), no when-not-to-use case, and no named alternative for single-node inserts or moves.

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