Skip to main content
Glama
Sign In
stitch-pro-mcp

stitch-pro-mcp

by LuciferDono
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create Stitch Project

sp_create_project

Create a new Stitch project to obtain a project identifier, required for initiating generation and automation tasks.

Instructions

Create a new Stitch project. Returns the project ID needed for sp_generate and sp_auto.

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": {
      "title": "<title>"
    },
    "name": "sp_create_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesName for the new Stitch project

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations provide that it's not read-only, not destructive, not idempotent. Description adds that it returns a project ID needed by other tools, but doesn't disclose additional traits like auth requirements.

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 sentences, front-loaded purpose, no redundant information. Every word earns its place.

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 simple creation tool with one parameter and no output schema, the description explains functionality, return value, and relationship to sibling tools, making it fully complete.

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 100% with a clear parameter description. The description does not add extra meaning beyond the schema for the single parameter.

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 action (create), resource (Stitch project), and output (project ID), distinguishing it from siblings like sp_projects (list) and sp_generate (uses project ID).

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?

Implicitly suggests using this tool before sp_generate and sp_auto, but lacks explicit when-not or alternative guidance. Still clear given sibling context.

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