Skip to main content
Glama
Sign In

Multiplayer Agent

by com.multiplayeragent
OverviewDiscussionsAdmin

Get authoritative logic logs

get_room_logs
Read-only

Returns recent runtime errors from a room's deployed logic (newest first), so you can self-fix after a deploy without joining the room. Errors also surface in state.shared.__error.

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": {
      "roomName": "<roomName>"
    },
    "name": "get_room_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameNoWhich game to act on: its publishable key (pk_…) or its exact name. Defaults to the x-mp-game header, then your primary game.
limitNoMax log lines (default 50).
roomNameYesThe room name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real context beyond them: results are newest-first, no room join is required, and the same errors also appear in state.shared.__error.

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 tight sentences. The core behavior and ordering are front-loaded, and the follow-on sentence about state.shared.__error carries genuine, non-redundant information.

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?

With no output schema, the description appropriately sketches the return (recent runtime errors, newest first) and notes the alternate error surface. For a simple three-parameter read tool this is nearly complete, lacking only detail on error entry shape or retention window.

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%, so game, limit, and roomName are already fully documented with defaults and bounds. The description only implicitly touches the room parameter and adds nothing about limit or game, so baseline 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?

States a specific verb and resource: 'Returns recent runtime errors from a room's deployed logic', with ordering ('newest first'). An agent can distinguish this diagnostics tool from list_room_logic and deploy_room_logic without opening any schema.

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

Usage Guidelines4/5

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

Gives a clear situation for use ('self-fix after a deploy without joining the room'), which tells the agent when this tool is valuable. It stops short of naming an alternative tool or an explicit when-not, so it falls just below the top band.

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

All Multiplayer Agent toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources