cp77wb-mcp

Overview Schema Source Related Servers Discussions Admin

wb_live_raycast

Casts rays through World Builder’s live scene intersection system to detect geometry, using the current first-person camera or a custom origin and direction.

Instructions

Raycast through World Builder's live scene intersection system; camera mode uses the current FPP camera.

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_raycast"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	No
`dir_x`	No
`dir_y`	No
`dir_z`	No
`rpc_dir`	Yes
`timeout`	No
`origin_x`	No
`origin_y`	No
`origin_z`	No
`use_physical`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Nov 9, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden and discloses almost nothing: no mention of permission requirements, what happens on a miss, whether the result is a single hit or a list, or how the RPC channel to the live editor must be established. Only the camera-mode behavior is hinted at.

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

Conciseness3/5

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

The single sentence is compact and front-loads the verb, but it is a fragment that omits clarification of the enum-based mode branch and required parameters. Brevity here reads as under-specification rather than disciplined conciseness.

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 10-parameter tool with no annotations and no output schema, the description is far too thin. An agent cannot tell what geometry inputs are mandatory when mode is 'custom', nor what the call produces, so it would likely need to guess or trial-and-error.

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 10 parameters, including the required 'rpc_dir', so the description should compensate but barely does. It implies the purpose of 'mode' (camera vs custom direction) but leaves dir_x/y/z, origin_x/y/z, use_physical, and timeout completely unexplained.

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 names a specific verb-resource pair: raycasting against World Builder's 'live scene intersection system'. It distinguishes itself well from siblings since no other listed tool performs raycasts, though it never states what a raycast returns (hit actor, position, material).

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 guidance on when to use this versus alternatives like wb_live_selection or wb_find, nor any stated prerequisites such as needing a connected live session. The only clause, 'camera mode uses the current FPP camera', describes behavior of one mode rather than when to choose the tool.

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

Deploy Server