Skip to main content
Glama
Sign In
devuniverse-mcp

devuniverse-mcp

by joeshwoa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Ingest a reference URL or video

ingest_reference

Extract design patterns (palette, typography, interactions) from a reference URL or video, then generate a rebuild plan for your project. Optionally blend the palette into your project tokens.

Instructions

Reverse-engineer the patterns of a reference the user provides: palette, typography, framework/interaction fingerprint (three.js, GSAP ScrollTrigger, scroll-snap, WebGL…), structure, and an equivalent-rebuild plan mapped onto devuniverse modules. Videos get ffmpeg keyframe + palette analysis when ffmpeg is present. Pattern-level only — protected artwork and trade dress are never copied. apply_theme=true blends the extracted palette into the project tokens.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPublic page you have the right to study.
video_pathNoLocal video file demonstrating the desired interaction.
apply_themeNo
project_dirYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that the tool only analyzes patterns and never copies protected artwork/trade dress, and mentions ffmpeg keyframe analysis when present. However, it does not describe side effects like file modifications or output format.

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 only three sentences, front-loaded with the core purpose. Every sentence adds value, including the caveat about protected works and the apply_theme behavior. No wasted words.

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

Completeness3/5

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

The tool has 4 parameters and no output schema. The description explains the core function and some param semantics, but does not describe what the tool returns (e.g., a plan text, updated files) or error conditions. Given the lack of annotations, more detail on output would improve completeness.

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?

Schema description coverage is 50% (url and video_path have descriptions). The description adds meaning beyond schema: it explains that apply_theme blends the extracted palette into project tokens and clarifies the purpose of url and video_path as input references. project_dir lacks explanation but is required.

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 uses specific verbs ('reverse-engineer the patterns') and identifies concrete resources (palette, typography, framework/interaction fingerprint). It clearly distinguishes from siblings by focusing on pattern analysis, not compliance, media generation, or other tasks listed in sibling tools.

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 usage when a user provides a reference URL or video for studying patterns. It mentions ffmpeg analysis for videos and the apply_theme option, but does not explicitly state when to avoid this tool or suggest alternative tools from the sibling list.

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