Skip to main content
Glama
Sign In
devuniverse-mcp

devuniverse-mcp

by joeshwoa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Generate the immersive 3D deep-scroll Flutter module

generate_spatial_module

Generate spatial canvas code with scroll-driven Z-axis camera, Matrix4 parallax layers, starfield, and snap-point rooms. Optionally include flutter_scene/flutter_cube mesh stages and Rive HUD overlay.

Instructions

Emit the spatial canvas code (scroll-driven Z-axis camera, Matrix4 perspective parallax layers, CustomPainter starfield, snap-point rooms, reduced-motion fallback; optional flutter_scene/flutter_cube mesh stage and Rive HUD) into an existing project or a fresh module directory.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "generate_spatial_module"
  }
}

Input Schema

NameRequiredDescriptionDefault
riveNoInclude the Rive HUD overlay seam.
project_dirNoExisting devuniverse project to write into (files land under app/). Omit to create a standalone module.
depth_layersNo
project_nameNoDisplay name used inside the demo journey.Spatial Canvas
mesh_rendererNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description must fully disclose behavioral traits. It mentions optional mesh renderers and Rive HUD, but lacks details on file overwriting, required permissions, error handling, or side effects. The description gives a sense of what is generated but not the behavior during generation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence of about 45 words, listing many features. While informative, it could be more concise or structured (e.g., bullet points) for easier scanning. The information density is high but the presentation is dense.

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

Completeness2/5

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

Given 5 parameters, no output schema, and no annotations, the description should provide more comprehensive coverage. It does not explain the depth_layers parameter, the return value or success indicators, nor does it address prerequisites (e.g., Flutter setup). The description leaves significant gaps for an agent to invoke the tool correctly.

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 description coverage is 60% (3 of 5 parameters have descriptions). The tool description adds meaning for mesh_renderer and rive by referring to them as optional, and for project_dir by distinguishing existing project vs. standalone module. However, depth_layers and project_name are not explained beyond their schema defaults, missing an opportunity to clarify their role in the generated output.

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 function: generating an immersive 3D deep-scroll Flutter module. It lists specific features (scroll-driven Z-axis camera, Matrix4 parallax, CustomPainter starfield, etc.) and distinguishes the tool from siblings like audit_compliance or generate_compliance_docs by focusing on code generation for spatial canvas.

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 notes that the tool can target an existing project or a fresh module directory, providing some usage context. However, it does not explicitly state when not to use the tool or mention alternatives. Given the sibling tools are quite different, the guidance is clear enough for typical use.

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