stitch-pro-mcp

Convert to Svelte

sp_to_svelte

Read-onlyIdempotent

Converts HTML/Tailwind markup into SvelteKit components with Svelte 5 runes ($state) and optional shadcn, Radix, or MUI library mapping.

Instructions

Convert HTML/Tailwind to SvelteKit components with Svelte 5 runes ($state) and optional component library mapping

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>"
    },
    "name": "sp_to_svelte"
  }
}

Input Schema

Name	Required	Description	Default
`html`	Yes	HTML/Tailwind source to convert
`componentLibrary`	No		none
`appRouter`	No	Use Next.js App Router (React only)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0May 26, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that the conversion uses Svelte 5 runes and optional library mapping, which is useful but does not deeply elaborate on behavioral traits like output format or side effects.

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?

A single, front-loaded sentence that efficiently conveys the tool's purpose and key features with 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?

Given three parameters and the presence of annotations, the description is fairly complete, covering the conversion target, framework specifics, and optional library mapping. However, it lacks details on output format and does not address the potentially misleading appRouter parameter.

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%, so baseline is 3. The description mentions 'optional component library mapping' correlating to the componentLibrary parameter, but does not clarify the appRouter parameter (which is for Next.js, potentially confusing in a Svelte context).

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/Tailwind to SvelteKit components with Svelte 5 runes and optional library mapping. It distinguishes from siblings like sp_to_react and sp_to_vue by specifying the target framework.

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?

The description implies use when targeting SvelteKit but does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions or prerequisites.

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

Deploy Server