Skip to main content
Glama
Sign In
cp77wb-mcp

cp77wb-mcp

by 0xra0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

wb_get

Read project statistics or inspect a single Cyberpunk 2077 World Builder element by path to retrieve its details.

Instructions

Read project stats or one World Builder element by path.

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>"
    },
    "name": "wb_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYes
pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. "Read" implies a non-mutating operation, but the description says nothing about permissions, error behavior, the shape of returned data, or what happens when path is omitted or invalid.

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?

The description is a single front-loaded sentence with no filler. Every word contributes to the stated purpose.

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?

With no annotations, no output schema, and no schema parameter descriptions, the definition is too sparse. It does not explain the required file parameter, optional path semantics, return values, or error conditions needed for reliable invocation.

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%, so the description must compensate for undocumented parameters. It gives some meaning to "path" as an element selector, but the required "file" parameter is completely undefined, and the optional path behavior and path format are not explained.

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 gives a specific verb, "Read", and two concrete resources: project stats or one World Builder element by path. It distinguishes this from the many mutation-oriented sibling tools, but it does not differentiate it from read-oriented siblings such as wb_tree, wb_find, or wb_live_state.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to use this tool instead of alternatives. The word "or" hints that omitting path may return project stats and supplying path may return one element, but that conditional behavior is never stated.

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