Skip to main content
Glama
Sign In
Universal Game Modder

Universal Game Modder

by doritoman90000
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

gorebox_list_mods

Lists installed GoreBox mods, including their info.json and file structure, to help you manage and troubleshoot mod setups.

Instructions

List all installed GoreBox mods with their info.json contents and file structure.

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": {
      "mods_dir": "<mods_dir>"
    },
    "name": "gorebox_list_mods"
  }
}

Input Schema

NameRequiredDescriptionDefault
mods_dirYesPath to the game Mods directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.3/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 full burden. It does disclose useful output behavior (returns info.json contents plus file structure), but says nothing about read-only safety, required permissions, or how incomplete/missing mod directories are handled.

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?

One front-loaded sentence with zero filler; the verb, resource, and returned content are all packed into a single readable clause.

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?

For a simple one-parameter list tool with no output schema, the description covers the basic return surface (info.json and file structure) but is thin on the shape of results and error behavior. It is adequate but leaves gaps an agent might want when interpreting output.

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?

There is a single parameter with 100% schema description coverage ('Path to the game Mods directory'), so the schema already documents it. The description adds no format, path-style, or defaulting details beyond the schema, which is the expected baseline when schema coverage is high.

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 names a specific verb (List) and resource (installed GoreBox mods) and clarifies the scope by stating it returns info.json contents and file structure. It is inherently distinguishable from generation siblings like gorebox_generate_mod, but it never explicitly contrasts with them or with any related listing tool.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternative tools. The sentence only states what the tool does, leaving the agent to infer when listing mods is appropriate versus other gorebox_* or asset-inspection tools.

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