Skip to main content
Glama
Sign In
cp77wb-mcp

cp77wb-mcp

by 0xra0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

wb_build_pack

Preview or run WolvenKit CLI/cp77tools packing after a verified Object Spawner import; run defaults to false for preview mode.

Instructions

Preview or run WolvenKit CLI/cp77tools pack after verified Object Spawner import. run=false 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": {
      "workspace": "<workspace>"
    },
    "name": "wb_build_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
cliNo
runNo
outputNo
timeoutNo
workspaceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses preview-vs-run and the default, but does not explain side effects, whether preview writes anything, external CLI requirements, failure behavior, or what run=true actually changes on disk.

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 short sentences with the operational verb and the default behavior front-loaded. There is no redundant or filler wording.

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?

For a tool with five undocumented parameters, no annotations, and no output schema, the description is too thin. It omits the meaning of workspace, output path behavior, timeout semantics, and what a preview returns or displays.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters. The description only clarifies 'run=false by default'; workspace, cli, output, and timeout remain undocumented, so it does not compensate for the schema gap.

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?

The description states a specific verb and resource: preview or run a WolvenKit CLI/cp77tools pack. The phrase 'after verified Object Spawner import' narrows the context, though it does not explicitly distinguish this from nearby siblings such as wb_build_package or wb_build_prepare.

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?

It gives a clear prerequisite ('after verified Object Spawner import') and explains the default preview behavior via 'run=false by default.' It does not name alternatives or exclusions, so the agent must infer when to choose this over other build/package tools.

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