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

arma3-wiki MCP Server

by ScottTMConnors
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search

Find Arma 3 SQF commands and event handlers by keyword across names, groups, and full text; all query words must match.

Instructions

Keyword search over command/event names, groups and full text. All words must match. kind: all | commands | events. Name matches rank first.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoall
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does meaningful work: it discloses AND semantics ('All words must match') and the ranking rule ('Name matches rank first'), which the agent could not infer from the schema. It stops short of stating that this is a read-only, side-effect-free operation and says nothing about how the limit behaves.

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 compact sentences, each front-loaded with the highest-value information: what is searched, the matching rule, the kind filter, and the ranking. No filler or redundant restatement of the tool name.

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

Completeness3/5

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

The presence of an output schema removes the need to document return values, and the description covers matching and ranking well. However, for a three-parameter search tool with a sibling set of lookups, the missing guidance on limit behavior and on selecting this tool over the lookup tools leaves a real gap.

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 coverage is 0%, so the description must compensate, and it does for two of three parameters: it defines what 'query' matches against and enumerates the valid 'kind' values, which the schema leaves as a bare string with a default. The 'limit' parameter is left entirely unexplained in both places.

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 concrete verb (keyword search) and enumerates the resources searched: command/event names, groups, and full text. That distinguishes it in spirit from the exact-match siblings lookup_command and lookup_event, though it never names them 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?

The 'kind: all | commands | events' hint implies how to narrow the search, but there is no explicit statement of when to reach for this tool versus lookup_command, lookup_event, or list_group. The agent must infer that this is the fuzzy/keyword path and siblings are the exact-match path.

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