Skip to main content
Glama
Sign In

Multiplayer Agent

by com.multiplayeragent
OverviewDiscussionsAdmin

Post highlights to Discord or Slack

set_highlight_webhook
Idempotent

Set where the game's highlights post: a Discord channel webhook (Server Settings → Integrations → Webhooks → Copy URL) or a Slack incoming webhook. Server logic posts with highlight(type, text, data), e.g. highlight("hard-clear", "Mia cleared Level 9 on one life"); the server decided it happened, so players can't fake one. Sends a test post and saves only if it is accepted. The URL is a credential: ask the user to paste it, and it is only ever shown back masked. Pass null to stop posting. Limits: 6 highlights a minute per room, 60 posts an hour per game (the rest are still recorded; see get_live_ops).

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": {
      "url": "<url>"
    },
    "name": "set_highlight_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYeshttps://discord.com/api/webhooks/… or https://hooks.slack.com/services/…, or null to clear.
gameNoWhich game to act on: its publishable key (pk_…) or its exact name. Defaults to the x-mp-game header, then your primary game.

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?

Goes well past the annotations: discloses that a test post is sent and the setting is saved only if accepted, that the URL is a credential shown back masked, and that posting is server-authoritative so players cannot fake highlights. Rate limits (6/min per room, 60/hr per game) and the fact that excess highlights are still recorded add operational context an agent cannot infer.

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-loads what gets configured before unpacking credentials and limits, and nearly every sentence carries distinct information. The highlight() call example is slightly more illustrative than strictly necessary, but it grounds the concept of a server-decided highlight.

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?

For a two-parameter write tool with no output schema, this covers everything an agent needs: accepted URL forms, the verification-then-save behavior, credential handling, the clear path, rate limits, and a pointer to get_live_ops for recorded-but-unsent highlights. No material gap remains.

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; the description adds real value by framing the url parameter as a credential the user must paste and never a value the agent should echo. The null-to-clear semantic and the game parameter's header default are left to the schema, so it lands just above baseline.

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?

Names a specific verb and resource (set where highlights post) and enumerates the two supported destinations, Discord channel webhook and Slack incoming webhook. The highlight(type, text, data) example makes concrete what is being routed, so it is unmistakable against siblings like set_live_config or get_live_ops.

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?

Clearly states the config action, gives the Discord navigation path to obtain a URL, and explicitly says to pass null to stop posting — a real when/when-not signal. It does not name an alternative sibling (e.g. set_live_config) for other notification settings, so it stops short of full routing guidance.

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