mcp-server-nuxt

Overview Schema Source Related Servers Discussions Admin

add_nuxt_module

Add a Nuxt module to the modules array in nuxt.config, optionally with options. Returns a diff; dry-run by default so changes can be reviewed before writing.

Instructions

Add a Nuxt module to the modules array in nuxt.config, optionally with options. Returns a diff; dry-run by default.

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

Input Schema

Name	Required	Description
`name`	Yes	Module name, e.g. @nuxtjs/i18n
`dryRun`	No	When true (default), return the planned change without writing
`options`	No	Optional module options as a JSON object string, e.g. {"locales": ["en"]}

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose two important behaviors: the default is a dry run, and the tool returns a diff rather than silently mutating config. It leaves out idempotency (what happens if the module is already listed) and validation/failure behavior.

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?

A single tight sentence that front-loads the action, then the location, then the return and default behavior. No filler and nothing repeated from the schema.

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 3-parameter config-mutation tool, the description covers the target file, the mutation site, the return value, and the safe default, and an output schema is absent but the 'returns a diff' note compensates. The remaining gap is the relationship to update_config and duplicate-module handling.

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 coverage is 100% with per-parameter descriptions including format examples, so the schema does the heavy lifting. The phrase 'optionally with options' adds only the optionality already visible in the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Add a Nuxt module to the modules array in nuxt.config'), which is precise and distinguishable from generic config tools. It stops short of naming the sibling it replaces (e.g. update_config) so the boundary is left to inference.

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?

'dry-run by default' implies a preview-then-apply workflow, which is useful implied guidance. However, the description never states when to prefer this over update_config or list_modules, nor any prerequisites such as the module already being installed or resolvable.

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