Skip to main content
Glama
vuluu2k

sbuilder-mcp

by vuluu2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sb_bind

Bind a node to real store data so the page shows actual products, not placeholder text. action makes a button a purchase control.

Instructions

Bind a node to real store data so the page shows actual products, not placeholder text. action makes a button a purchase control.

Input Schema

NameRequiredDescriptionDefault
idYes
fieldYesWhere the value lands, always "specials.<key>"
forceNoOverride a render-inference guard; reported as forced
actionNoPass product.id + specials.boundProductId
sourceYese.g. article.author, article.categories, article.content, article.date; 94 in all, plus record.fld_<16 hex> for a Collections field; a wrong one is refused with the list
dry_runNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.89.0
    • changedInput schema / properties / source / description
      Previous value: -"e.g. article.author, article.categories, article.content, article.date; 79 in all, and a wrong one is refused with the list"New value: +"e.g. article.author, article.categories, article.content, article.date; 94 in all, plus record.fld_<16 hex> for a Collections field; a wrong one is refused with the list"
  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. Changed1 schema field changedv0.60.1
    • changedInput schema / properties / source / description
      Previous value: -"e.g. article.author, article.categories, article.content, article.date; 78 in all, and a wrong one is refused with the list"New value: +"e.g. article.author, article.categories, article.content, article.date; 79 in all, and a wrong one is refused with the list"
  4. Changed2 schema fields changedv0.12.0
    • addedInput schema / properties / action
      Added value: +{
+  "description": "Pass product.id + specials.boundProductId",
+  "enum": [
+    "add_to_cart",
+    "buy_now"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / source / description
      Previous value: -"One of: article.author, article.categories, article.content, article.date, article.image, article.summary, article.tags, article.title, article.url, category.description, category.image, category.title, category.url, product.compareAtCents, product.compareAtPrice, product.description, product.id, product.image, product.images, product.price, product.priceCents, product.ratingAverage, product.ratingCount, product.title, product.url, product.vendor"New value: +"e.g. article.author, article.categories, article.content, article.date; 78 in all, and a wrong one is refused with the list"
  5. First observedv0.1.4

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the agent knows this is a non-destructive write. The description adds the effect on rendering (placeholder text becomes real data) and implies validation via the schema note that a wrong source is refused. It does not disclose what happens to existing bindings, whether the change is reversible, or undo behavior, so credit is limited.

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?

Two tight sentences with the primary outcome front-loaded and zero filler. It is efficient, though the second sentence is a fairly thin addition.

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?

For a 6-parameter mutation tool with no output schema, the description is very thin: it omits the dry_run/force workflow, how bindings are keyed by id and field, and any interaction with the surrounding page/node tools. An agent would need to infer the invocation flow almost entirely from the schema.

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 coverage is 67%, with the schema already documenting field, force, action, and source in useful detail. The description's only parameter-level addition is the action/purchase-control note, which largely restates the enum's intent. It neither documents id nor dry_run, so it does not compensate for the partial coverage.

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?

Names a specific verb (bind) and resource (a node to real store data) and states the user-visible outcome (real products instead of placeholder text). It does not differentiate itself from write siblings like sb_set or sb_connect, but the purpose is clear.

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

Usage Guidelines2/5

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

The description never says when to choose sb_bind over alternatives such as sb_set, sb_connect, or sb_store, nor does it state prerequisites (e.g. that a store/source must exist). The only routing hint, 'action makes a button a purchase control', explains a parameter rather than the when-to-use decision.

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