Skip to main content
Glama
Sign In
MCPBridge Server

MCPBridge Server

by RBG-WebDesign
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

gameplay_pie_start

Launch a Play In Editor (PIE) session and wait until the game world is ready. Returns success when the PIE-ready marker appears, so you can proceed with gameplay tests or telemetry snapshots.

Instructions

Launch a Play In Editor (PIE) session and wait until the game world is ready (up to 30s). Returns success once the PIE-ready log marker is found. Call this before gameplay_run_acceptance_tests or gameplay_telemetry_snapshot.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gameplay_pie_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
level_pathNoContent path of the level to load before PIE (e.g. /Game/Maps/Gameplay). If omitted, uses the current level.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the transparency burden. It discloses the blocking wait up to 30s, the success condition (PIE-ready log marker found), and the purpose. It does not mention failure modes, side effects on existing PIE sessions, or permissions, but the disclosed behavior is meaningful and goes beyond a bare 'start'.

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 sentences, front-loaded with the core action, then a success condition, then usage guidance. Every sentence contributes information, with no fluff or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with one optional parameter, no output schema, and no annotations, the description covers the main behavior, timeout, success marker, and intended usage. It lacks failure conditions and edge cases (e.g., what if PIE is already running), but is otherwise fairly complete for an agent to invoke it correctly.

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

Parameters3/5

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

Schema description coverage is 100% for the single optional parameter level_path, which is fully documented in the schema. The description adds no additional parameter semantics, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Launch a Play In Editor (PIE) session') and the resource (game world), and includes the waiting behavior. It distinguishes from siblings by naming dependent tools (gameplay_run_acceptance_tests, gameplay_telemetry_snapshot) that should follow this start.

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

Usage Guidelines5/5

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

Explicitly states when to use the tool: 'Call this before gameplay_run_acceptance_tests or gameplay_telemetry_snapshot.' This provides clear context for invocation order and prerequisites, even though it doesn't list when-not-to-use alternatives.

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