Skip to main content
Glama
Sign In
cp77wb-mcp

cp77wb-mcp

by 0xra0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

wb_live_ping

Pings the optional Cyberpunk 2077 World Builder CET file-RPC companion to verify connectivity and reports whether v0.5 spatial and history capabilities are available.

Instructions

Ping the optional cp77wb CET file-RPC companion and report v0.5 spatial/history capabilities.

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": {
      "rpc_dir": "<rpc_dir>"
    },
    "name": "wb_live_ping"
  }
}

Input Schema

NameRequiredDescriptionDefault
rpc_dirYes
timeoutNo

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 supplied, so the description carries the full burden. It does not disclose what happens when the companion is absent (error versus a negative result), what the reported 'capabilities' look like, or whether the call has side effects — all material for a probe tool with zero annotation coverage.

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?

A single front-loaded sentence with no filler or repetition. It is compact and readable, though the condensed jargon ('cp77wb CET file-RPC') slightly reduces first-pass comprehension.

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?

There is no output schema and no annotations, so the description is the only source of behavioral information, yet it omits return shape, failure behavior, and both parameter meanings. For a two-parameter probe tool this leaves an agent under-equipped to call it correctly.

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

Parameters1/5

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

Schema description coverage is 0%: the required 'rpc_dir' string and the 'timeout' number are completely undocumented. The description never mentions either parameter, so an agent must guess the directory format and the timeout unit (seconds? milliseconds?). This is the one place the description needed to compensate and it does not.

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 ('Ping') against a named resource (the optional cp77wb CET file-RPC companion) and a specific payload ('report v0.5 spatial/history capabilities'). It is clearly distinguishable from the many wb_live_* siblings, which are mutation/query operations, though the domain jargon assumes the agent already knows what the companion is.

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?

The word 'optional' implies this is a connectivity/probe check to run before relying on other wb_live_* tools, but that routing is left implicit. There is no explicit statement of when to call it versus e.g. wb_live_state, nor what to do if the ping fails.

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