argo-mcp

Add co-GM

add_co_gm

Send a user an assistant GM (co-GM) offer for a campaign. This does NOT add them immediately: the target must accept the offer before they become an assistant GM. Owner-only — the calling user must be the campaign's primary GM. Maximum 5 co-GMs per campaign.

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": {
      "campaignId": "<campaignId>",
      "userId": "<userId>"
    },
    "name": "add_co_gm"
  }
}

Input Schema

Name	Required	Description	Default
`userId`	Yes	Argo user ID of the user to promote to co-GM. Must be an existing user.
`campaignId`	Yes	Campaign ID.

Output Schema

Name	Required	Description	Default
`id`	Yes
`ruleSystem`	No
`campaignName`	Yes
`gameMasterId`	Yes
`gameSystemSlug`	No
`coGameMasterIds`	No
`campaignDescription`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 14, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses key behaviors: the offer-based flow, the acceptance requirement, the owner-only restriction, and the limit of 5 co-GMs. These are essential for the agent to understand the tool's side effects and constraints.

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?

Three concise sentences deliver the core purpose, a critical caveat, and two constraints. Every sentence earns its place with no redundancy or filler.

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 simple offer-sending tool, the description covers all behavioral requirements: the offer mechanism, the need for acceptance, the owner-only rule, and the cap. An output schema exists, so return value details are not the description's responsibility. The description is complete for the tool's complexity.

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?

The input schema already documents both parameters with 100% coverage, so the description does not need to elaborate. The mention of 'user' and 'campaign' aligns with the schema but adds no additional parameter-level semantics beyond what the schema provides.

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 'Send a user an assistant GM (co-GM) offer for a campaign,' providing a specific verb and resource. It also distinguishes itself from sibling tools by explicitly noting it does NOT add immediately, which prevents confusion with any direct-add interpretation.

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?

The description gives explicit usage guidance: it clarifies that the target must accept the offer, so it is not for immediate addition. It also specifies an owner-only precondition and a maximum cap of 5 co-GMs, giving clear conditions for when this tool is appropriate.

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

All argo-mcp tools Inspect

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.