Skip to main content
Glama
Sign In
Galgame MCP

Galgame MCP

by YeXuanHs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

re_rizin

Perform headless Rizin analysis on PE/EXE/DLL/TPM files to hunt for crypto and Cx strings. Customize with rz commands and timeout settings.

Instructions

Headless Rizin analysis (aaa + crypto/Cx string hunt by default).

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

Input Schema

NameRequiredDescriptionDefault
pathYesPE/EXE/DLL/TPM
timeoutNoSeconds (default 180)
commandsNoCustom rz commands; omit for default pack

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are present, so the description carries the full burden. It mentions headless mode and default analysis commands, but does not disclose whether the tool is read-only, what output it returns, or any side effects. This is a significant gap for a tool that executes external commands.

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?

The description is a single sentence that is front-loaded with the tool's name and default behavior, containing no wasted words.

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?

With no output schema, the description should at least indicate what the tool returns or achieves. It does not mention output format, and the phrase 'crypto/Cx string hunt' is opaque without domain knowledge. For a complex tool with 3 parameters, the description is insufficiently complete.

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?

Schema descriptions cover all 3 parameters (path, timeout, commands), so the baseline is 3. The description adds no new parameter semantics beyond the schema, though it aligns with the 'commands' omission default.

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 clearly identifies the tool as headless Rizin analysis and specifies the default command set (aaa + crypto/Cx string hunt). It is distinct from siblings like re_ghidra_headless, though it doesn't explicitly contrast them.

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?

No guidance is provided on when to use this tool versus alternatives like re_ghidra_headless or re_disasm. The mention of 'default' implies custom commands are possible, but there are no explicit context cues or exclusions.

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