ultramock-mcp

This server has been deprecated

unofficial mcp, unmaintained.

Create project

create_project

Create a new mockup project, optionally using a template to pre-configure device, camera angle, and lighting.

Instructions

Create a new mockup project. Optionally seed it from a template (see list_templates) so it starts with a device, camera angle and lighting already configured.

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

Input Schema

Name	Required	Description	Default
`name`	Yes	Project name.
`fromTemplateId`	No	Optional template id to seed the project from.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 8, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description bears the full burden. It discloses that the tool creates a new project and optionally seeds from a template, but lacks details on side effects, permissions required, or whether names must be unique. This is adequate for a creation tool but not comprehensive.

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 with no unnecessary words. First sentence states the core action, second adds an optional feature with a reference to a sibling tool. Highly efficient.

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?

For a simple tool with two parameters and no output schema, the description covers the main functionality and optional enhancement. It references a sibling for more details. It could mention the return value, but that is not critical.

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 covers both parameters with descriptions. The description adds value by explaining that 'fromTemplateId' allows seeding with preconfigured device, camera angle, and lighting, which goes beyond the schema's brief description.

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 verb 'Create' and the resource 'mockup project', and distinguishes from siblings like 'duplicate_project' by specifying it creates a new project. It also adds the unique optional feature of seeding from a template.

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?

The description tells when to use this tool (to create a new project) and references 'list_templates' for the seeding option, providing implicit guidance. However, it does not explicitly contrast with siblings like 'duplicate_project' or state when not to use it.

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

Deploy Server