stitch-pro-mcp

Smart Convert

sp_smart_convert

Read-onlyIdempotent

Converts HTML to React, Vue, or Svelte while automatically applying accessibility fixes and responsive adaptation through a built-in quality pipeline.

Instructions

Converts HTML to a framework, but auto-detects if it needs accessibility fixes and responsive adaptation first. Runs the full quality pipeline before conversion — no manual chaining needed.

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": {
      "html": "<html>",
      "framework": "<framework>"
    },
    "name": "sp_smart_convert"
  }
}

Input Schema

Name	Required	Description	Default
`html`	Yes	HTML to convert — auto-detects needed pre-processing
`framework`	Yes	Target framework
`componentLibrary`	No		none
`appRouter`	No	Next.js App Router (React only)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0May 26, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate read-only, non-destructive, idempotent. The description adds that it auto-detects and runs a quality pipeline, providing useful behavioral context beyond annotations.

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 concise sentences with key information front-loaded; no unnecessary words.

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

Completeness4/5

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

Describes the core value well, but lacks mention of output format or optional parameters like componentLibrary and appRouter.

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 high (75%), and the description doesn't add meaning beyond schema fields, like clarifying componentLibrary or appRouter purpose.

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 clearly states it converts HTML to a framework with auto-detection of accessibility and responsive needs, distinguishing it from sibling tools like sp_to_react or sp_a11y.

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?

It implies use when you want a one-step conversion with pre-processing, but does not explicitly mention when simpler alternatives like sp_to_react are preferable.

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

Deploy Server