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

arma3-wiki MCP Server

by ScottTMConnors
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_tutorials

Lists bundled Arma 3 scripting tutorials covering best practices, multiplayer scripting, and optimization so you can find relevant guidance without searching the wiki manually.

Instructions

List the bundled scripting tutorials (best practices, MP scripting, optimisation).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_tutorials"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

With no annotations, the description must carry the behavioral burden. The word "bundled" usefully signals static, packaged content rather than wiki-backed data (contrasting with wiki_status/refresh_wiki), but nothing is said about ordering, pagination, or whether results can change.

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?

A single front-loaded sentence with the verb and resource first and the parenthetical category detail last. Nothing is redundant or wasted.

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 zero-argument read tool with an output schema, the description covers purpose and content scope adequately. It could still note how the listing relates to get_tutorial, which is the natural next step.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description does not add any spurious input guidance.

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 uses a specific verb and resource ("List the bundled scripting tutorials") and even names the topical categories covered (best practices, MP scripting, optimisation). It is clearly distinct from get_tutorial, which retrieves one item, though it does not say so explicitly.

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 only implied: an agent can infer this is the discovery step before get_tutorial, but the description never states when to prefer it over search, lookup_command, or get_tutorial. There are no exclusions or prerequisites.

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