Skip to main content
Glama
Sign In
Galgame MCP

Galgame MCP

by YeXuanHs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

archive_list_formats

List all native archive format plugins and pack support to determine which file types can be processed.

Instructions

List all native archive format plugins and pack support.

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": "archive_list_formats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/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 burden. It clearly indicates a read-only enumeration action via 'List all,' but it does not disclose any additional behavioral traits such as whether it reflects runtime-discovered plugins or requires initialization.

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 sentence that is front-loaded with the verb 'List' and contains zero filler. Every word contributes meaning.

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 no-parameter, no-annotation, no-output-schema tool, the description clearly states what is listed and even specifies 'pack support' as an additional dimension. It is slightly terse but sufficient for the intended use case.

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 has zero parameters, and the schema already reflects that with 100% coverage. Baseline 4 applies because there is no parameter ambiguity for the description to resolve.

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?

Description uses the specific verb 'List' and identifies the resource as 'all native archive format plugins and pack support.' It clearly distinguishes from sibling tools like archive_list (which likely lists archive contents) and archive_probe (which likely probes a specific archive).

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 description implies usage: call this to see which archive formats are natively supported and whether packing is supported. However, it does not explicitly mention when not to use it or compare it with alternatives like audio_list_formats or vnt_list_formats.

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