Skip to main content
Glama
Sign In

argo-mcp

by io.github.Argo-RPG-Platform
OverviewDiscussionsAdmin

Add campaign to guild

add_campaign_to_guild

Add a campaign to a guild. Any active member of the guild can do this; the calling user must be the campaign's GM (enforced server-side).

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": {
      "guildId": "<guildId>",
      "campaignId": "<campaignId>"
    },
    "name": "add_campaign_to_guild"
  }
}

Input Schema

NameRequiredDescriptionDefault
guildIdYesGuild ID.
campaignIdYesCampaign ID to add to the guild.

Output Schema

NameRequiredDescriptionDefault
guildIdYes
successYes
campaignIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The description discloses authorization requirements (active membership and GM status enforced server-side), going beyond the annotations. It provides useful behavioral context without contradicting the settings.

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?

The description is exactly two sentences long, front-loaded with the action, and the second sentence adds necessary constraint information without redundancy.

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?

With a simple tool, full parameter documentation, and an output schema available, the description covers the essential purpose and usage constraints. No additional behavioral details are needed.

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 schema fully describes both parameters ('Guild ID' and 'Campaign ID to add to the guild'), so the description adds no parameter-specific meaning. Baseline of 3 is appropriate given 100% schema coverage.

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: 'Add a campaign to a guild' with a specific verb and resource. It is unambiguous and easily distinguished from sibling tools like add_co_gm or add_guild_calendar_event.

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?

It provides clear guidance on who can use the tool: any active guild member, with the calling user required to be the campaign's GM. This gives context for use, though it does not explicitly mention alternatives or when not to use it.

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

All argo-mcp 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