Skip to main content
Glama
Sign In
arma3-wiki MCP Server

arma3-wiki MCP Server

by ScottTMConnors
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_group

Lists commands in a specified Arma 3 wiki group, or all groups when passed an empty string, helping AI clients browse SQF command categories.

Instructions

List commands in a wiki group (e.g. 'Multiplayer', 'Particles'). Pass '' to list all groups.

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": {
      "group": "<group>"
    },
    "name": "list_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. The verb 'List' implies a read-only operation and the empty-string behavior is explicitly disclosed, but permissions, pagination, and invalid-group handling are not described. The output schema partially offsets this by covering return values.

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 two concise sentences with the main purpose front-loaded. Examples and the empty-string special case are included without unnecessary wording.

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

Completeness4/5

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

For a simple one-parameter list tool with an output schema, the description covers the core purpose and parameter semantics well. It stops short of describing behavior for invalid group names or pagination, but those are minor gaps for this complexity level.

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 description coverage is 0%, so the description must compensate for the sole group parameter. It does so by explaining that the parameter is a wiki group, giving examples, and defining the special empty-string value for listing all groups.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: list commands in a wiki group, with concrete examples like 'Multiplayer' and 'Particles'. It is clear what the tool does, but it does not explicitly differentiate itself from siblings such as lookup_command or search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied through the listing purpose and the instruction to pass '' to list all groups. However, it gives no explicit guidance on when to use this tool instead of lookup_command, search, or other siblings, and states no exclusions.

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

Deploy Server

Other Tools