argo-mcp

Get campaign

get_campaign

Read-onlyIdempotent

Retrieve details of an Argo campaign (name, description, rule system, co-GMs).

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>"
    },
    "name": "get_campaign"
  }
}

Input Schema

Name	Required	Description	Default
`campaignId`	Yes	The ID of the campaign to retrieve.

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.1/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds minimal behavioral context beyond the fact that it retrieves details; it does not disclose error cases, permissions, or pagination behavior. This is acceptable since the tool is a simple read operation with output schema available.

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 a single, well-structured sentence that front-loads the action and resource, and lists representative details. It is concise with no redundant or filler content.

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?

The tool is simple: one parameter, a clear read-only purpose, and an output schema that presumably documents the return structure. The description is complete for this simple tool, and annotations cover safety and idempotency. No additional context is 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 has 100% coverage of the single parameter (campaignId) with a clear description. The tool description adds no additional parameter semantics beyond that. Baseline of 3 is appropriate since the schema fully documents the parameter.

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 uses a specific verb ('Retrieve') and clearly identifies the resource ('an Argo campaign') along with the specific details returned (name, description, rule system, co-GMs). It clearly distinguishes from sibling tools like 'list_campaigns' (which lists campaigns) and 'update_campaign' (which modifies).

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?

The description implies usage for fetching details of a single campaign, which is clear from the verb 'get' and 'Retrieve details'. However, it does not explicitly state when to prefer this over alternatives like 'list_campaigns' or mention any contextual exclusions. The context is clear but not explicit about alternatives.

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.