Skip to main content
Glama
Sign In
cp77wb-mcp

cp77wb-mcp

by 0xra0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

wb_grid

Create a 3D rectangular array in a Cyberpunk 2077 World Builder file, using counts that include the source node. Preview changes by default; set write=true to apply.

Instructions

Create a 3D rectangular array; counts include source. Dry-run unless write=true.

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": {
      "file": "<file>",
      "path": "<path>",
      "count_x": "<count_x>",
      "count_y": "<count_y>",
      "count_z": "<count_z>"
    },
    "name": "wb_grid"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYes
pathYes
writeNo
step_xNo
step_yNo
step_zNo
count_xYes
count_yYes
count_zYes
keep_noderefsNo
noderef_prefixNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/5.0
Behavior3/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 it does disclose two useful traits: the operation dry-runs unless write=true, and counts are inclusive of the source object. However, it says nothing about what is actually created in the file, whether the operation is reversible, or what the response contains.

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

Conciseness4/5

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

Two tight clauses with zero filler, and the core action is front-loaded ahead of the safety caveat. It is efficient, though the brevity is partly the source of the missing parameter detail rather than pure economy.

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 an 11-parameter generative tool with no annotations, no output schema, and no schema descriptions, the definition is thin. An agent could infer the counts but would be guessing at grid spacing, noderef behavior, and what file/path must point to.

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 11 parameters, so the description must compensate and largely fails. It clarifies count_x/count_y/count_z semantics ('counts include source') and the role of write, but leaves step_x/step_y/step_z spacing, keep_noderefs, noderef_prefix, file, and path entirely undefined.

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: 'Create a 3D rectangular array'. The '3D rectangular' qualifier distinguishes it from the sibling array tools (wb_array, wb_radial_array, wb_path_array, wb_scatter) by implying a volumetric grid, though it never names those alternatives explicitly.

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?

Usage is only implied by the '3D rectangular' qualifier and the 'Dry-run unless write=true' note, which tells the agent the call is non-destructive by default. There is no explicit statement of when to prefer this over wb_array or wb_radial_array, and no prerequisites are given.

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