Skip to main content
Glama

sb_review

Read-only

Review a Store Builder page for broken visitor-facing content and checkout or order-flow blockers before marking it complete.

Instructions

What a VISITOR would meet on the open page (blank band, placeholder, dead binding) AND what stands between this store and a paid order (checkout page, gateway, delivery, a cart link). Run it before calling a page done; page_id: only that page.

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": "sb_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.103.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / page_id
      Added value: +{
      +  "type": "string"
      +}
  2. First observedv0.1.4

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true is consistent with an inspection tool, and the description correctly frames it as a check rather than a mutation. It adds useful domain detail about what is examined but says nothing about the nature of the findings or what output to expect. With annotations already carrying the read-only safety profile, a 3 fits.

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

Conciseness3/5

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

Two sentences with no filler, but they are dense and jargon-heavy ('blank band', 'dead binding'), requiring interpretation. The action verb and when-to-run guidance are pushed to the second sentence, so it is not front-loaded.

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?

For a review tool with no output schema, the description should signal the shape of the findings an agent will get back. It covers what is checked and when to run it, but the return behavior and whether it reports or fixes are left implicit.

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 documents nothing (0% coverage), but the description compensates by explaining that page_id restricts the review to that single page, implying the default covers the whole store. With only one optional parameter, that is sufficient to use it correctly.

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 concretely says what it detects: visitor-facing page defects (blank band, placeholder, dead binding) and store checkout blockers (checkout page, gateway, delivery, cart link). This goes well beyond the opaque name 'sb_review' and lets an agent distinguish it from siblings like sb_page_state or sb_look. It stops short of a clean verb ('reviews/audits'), staying in descriptive phrasing.

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?

'Run it before calling a page done' is an explicit trigger condition, and 'page_id: only that page' clarifies the scoped mode of use. It lacks explicit alternatives (e.g. sb_page_repair for fixing what it finds), so it does not reach the when/when-not bar of a 5.

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