Skip to main content
Glama
Sign In
devuniverse-mcp

devuniverse-mcp

by joeshwoa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Watch the asset drop zone

watch_assets

Monitor a directory and automatically trigger verification and theme adaptation when images are added. List active watchers without arguments.

Instructions

Start/stop the watcher on app/assets/incoming — any image dropped there re-runs verification and theme adaptation automatically. Call without project_dir to list active watchers.

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": "watch_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledNo
project_dirNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. Describes toggling and automatic re-run behavior, but lacks details on side effects, permissions, or process implications.

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 with main action, no wasted words. Efficiently conveys core information.

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 toggle tool with no output schema and no annotations, description covers main purpose, parameter behavior, and automatic effects. Missing return value or error conditions, but adequately complete given low complexity.

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 has 0% description coverage, but description adds meaning: explains that removing project_dir changes behavior to listing. Adds value beyond schema structure.

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?

Description clearly states the tool starts/stops a watcher on a specific path, and lists active watchers when no project_dir. This distinguishes it from siblings like verify_assets or generate_media_asset.

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?

Provides clear usage context: start/stop watcher, and listing watchers without project_dir. However, no explicit when-not-to-use or alternatives among siblings.

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