stitch-pro-mcp

Responsive Adaptation

sp_responsive

Read-onlyIdempotent

Takes HTML as input and adds Tailwind breakpoints to ensure it adapts to mobile, tablet, and desktop screens.

Instructions

Make HTML responsive by injecting Tailwind breakpoints for mobile, tablet, and desktop

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_responsive"
  }
}

Input Schema

Name	Required	Description	Default
`html`	Yes	HTML to make responsive

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0May 26, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations (readOnlyHint: true, destructiveHint: false, idempotentHint: true) indicate a safe, non-destructive operation. The description adds context by specifying the transformation (injecting Tailwind breakpoints), aligning well with the 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?

The description is a single, concise sentence that directly conveys the tool's purpose without any filler. It is front-loaded and efficient.

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

Completeness5/5

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

For a tool with one simple parameter, no output schema, and straightforward behavior, the description provides all necessary context. The agent can correctly understand what input to provide and what output to expect.

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?

The only parameter 'html' is fully described in the schema (100% coverage). The tool description does not add extra detail beyond the schema, which is acceptable given the high coverage.

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 the tool's action ('Make HTML responsive') using specific verb and resource, and distinguishes from sibling tools (e.g., sp_a11y, sp_analyze) by focusing on responsive adaptation with Tailwind breakpoints.

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 when to use (making HTML responsive) but does not explicitly state when not to use or mention alternatives. No guidance is given for edge cases 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