Skip to main content
Glama
vuluu2k

sbuilder-mcp

by vuluu2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sb_theme

Read or update site-wide colors, text styles, and locale in one call. Unnamed token values are kept, so a single change repaints every page.

Instructions

The site's palette and type scale — the layer every element's style preset resolves from, so one token repaints every page at once. Call it with nothing to read what the site actually has. colors and text_styles PATCH the saved document: what you do not name is kept. locale sets the site's language (settings.locale, what is served from) — site-wide, every other setting kept.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colorsNoToken id -> CSS colour, e.g. { "heading": "#2E2A3B", "primary": "#E8557A" }
localeNoSite language tag, e.g. "vi" or "en"
dry_runNo
site_idNo
text_stylesNoText style slug -> base declarations, e.g. { "h1": { "fontSize": "48px" } }

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.69.0
    • addedInput schema / properties / locale
      Added value: +{
+  "description": "Site language tag, e.g. \"vi\" or \"en\"",
+  "type": "string"
+}
  2. Addedv0.32.0

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that colors and text_styles PATCH the saved document, that unspecified keys are preserved, and that locale applies site-wide. This is useful behavioral detail, though dry_run behavior is not explained and might have been valuable given the mutation-oriented operations.

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 compact, front-loaded with the tool's role, and every sentence adds functional value. The backticked parameter references are clear, and the patch semantics are stated with minimal wording.

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?

The core read/patch/locale behaviors are covered, but dry_run and site_id are not explained, and there is no output schema or return-format note. For a 5-parameter tool with no output schema, the description leaves meaningful gaps an agent would need to resolve.

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 schema already documents colors, locale, and text_styles, but the description adds meaning: it clarifies partial-update behavior and connects locale to settings.locale and <html lang>. This goes beyond the schema, though dry_run and site_id remain undefined in both places.

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 clearly identifies the tool as the site-wide palette and type scale layer, and gives specific verbs: read with no arguments, PATCH colors/text_styles, and set locale. It is clear about the resource and operations, though it does not explicitly differentiate from likely siblings like sb_look or sb_set.

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?

The description explains concrete call patterns: invoke with nothing to read, use colors/text_styles to PATCH, use locale for language. It gives clear context and partial-update semantics, but does not mention when to prefer a sibling tool or any exclusions.

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