Skip to main content
Glama
Sign In
Galgame MCP

Galgame MCP

by YeXuanHs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

xp3_re_analyze

Analyze an XP3 archive for cxdec/encryption symptoms and receive recommended next reverse engineering steps.

Instructions

Analyze one XP3 for cxdec/encryption symptoms and recommend next RE steps.

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": {
      "path": "<path>"
    },
    "name": "xp3_re_analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
sample_entriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description must convey safety and behavior, but it only says 'analyze' and 'recommend'; it does not state read-only status, side effects, limitations, or what 'symptoms' detection entails. This leaves important behavioral ambiguity.

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 no filler or redundant wording. Every clause contributes meaning.

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

Completeness2/5

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

For a two-parameter tool with no output schema or annotations, the description does not explain the optional parameter, return format, or prerequisites for meaningful use. It is minimally viable for selection but not for correct invocation beyond the required path.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description only indirectly covers 'path' via 'one XP3'; 'sample_entries' is completely unexplained. The agent cannot infer what sample_entries controls or its acceptable values from the description.

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 the specific verb 'Analyze' with a clear resource and goal ('one XP3', 'cxdec/encryption symptoms', 'recommend next RE steps'). It differentiates from raw extraction tools but does not explicitly name sibling alternatives, so it stops short of a 5.

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?

It implies use when analyzing a single XP3 to decide next RE work, but provides no explicit when-to-use/when-not-to-use or alternative tool guidance. The 'one XP3' scoping is the only usage context.

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