Skip to main content
Glama
Sign In

Multiplayer Agent

by com.multiplayeragent
OverviewDiscussionsAdmin

Get a game's live ops

get_live_ops
Read-only

Read a game's live ops: now (what players see right now: the merged config plus active and upcoming events), the base config, every scheduled event with its status (active / upcoming / ended), the highlight webhook (masked) and the 20 latest highlights with how each was delivered. Pass at to preview another instant (e.g. the middle of a weekend event) and room to see one room's view. Use it to verify every change you make.

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": "get_live_ops"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoISO-8601 instant to preview (default now).
gameNoWhich game to act on: its publishable key (pk_…) or its exact name. Defaults to the x-mp-game header, then your primary game.
roomNoResolve for this room (events limited to other rooms drop out). Default: game-wide.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already mark it read-only and non-open-world, and the description adds substantial context beyond that: the merged-config-plus-events return shape, event status taxonomy (active/upcoming/ended), that the webhook is masked, and that exactly 20 latest highlights are included with delivery status. It also warns that room scoping drops events targeted at other rooms — real behavioral consequence, not a restatement of annotations.

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?

Front-loaded with the core read operation, then the returned contents, then the parameter guidance — a logical order with no filler. The middle sentence is a long comma-separated inventory, which is dense but each clause carries distinct information, so it only barely costs a point.

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

Completeness5/5

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

There is no output schema, so the description must describe what comes back, and it does so thoroughly (now view, base config, scheduled events with statuses, masked webhook, recent highlights). Combined with the preview/room parameter guidance, an agent has everything needed to call it and interpret results.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description earns extra credit by explaining the intent behind parameters: previewing an arbitrary instant such as 'the middle of a weekend event' and filtering to a single room's resolved view. It does not restate the `game` parameter, which the schema already covers.

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 ('Read a game's live ops') and then enumerates exactly what that returns: merged config, scheduled events with status, webhook, highlights. It is clearly distinct from the write siblings (set_live_config, schedule_live_event) because it is framed as a read/verification operation.

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 an explicit operating directive — 'Use it to verify every change you make' — which ties it to the write siblings, and explains when to use the optional parameters ('Pass `at` to preview another instant', '`room` to see one room's view'). It lacks an explicit when-not-to-use statement or a named alternative for other scenarios, which keeps it off a 5.

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