vnyan-mcp

Overview Schema Source Related Servers Discussions Admin

VNyan UI

vnyan_ui

Read VNyan's active color theme or open native load/save dialogs to resolve a real local file path, blocking until user responds.

Instructions

Read the active color theme, or open a native load/save file dialog to resolve a real local file path (blocks until the user responds - use a generous timeout expectation). Source: plugin (live).

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

Input Schema

Name	Required	Description
`action`	Yes	Which UI operation to perform
`header`	No	Dialog title text shown to the user, for openLoadFileDialog/openSaveFileDialog
`extensions`	No	File extensions without the dot, e.g. ['png','jpg']

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 29, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It notes the blocking nature and timeout expectation for file dialogs, which is critical. It does not mention potential failure modes or return behavior, but it covers the most important aspect for an interactive UI tool.

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 concise sentences: the first lists the operations, the second provides essential behavioral context and source. Every word serves a purpose with no redundancy.

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?

Given no output schema, the description could be more specific about return values (e.g., what the theme operation returns). However, for a tool with only three enum actions, it provides enough context to use it effectively, and the blocking behavior is clearly communicated.

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?

All three parameters are fully described in the schema (100% coverage). The description adds context about blocking and file path resolution but does not significantly enhance the parameter meaning beyond the schema. Baseline 3 is appropriate.

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 two distinct operations: reading the active color theme and opening file dialogs to resolve file paths. It uses specific verbs ('read', 'open') and resource nouns ('color theme', 'file dialog'), and the sibling tools are all unrelated, so it is well-differentiated.

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 explicitly warns that the file dialog actions block until the user responds, advising a generous timeout. This is a key usage guideline. While it does not explicitly state when not to use it, the action enum makes the choice clear, and there are no overlapping siblings that require exclusion criteria.

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