Skip to main content
Glama
Sign In
Galgame MCP

Galgame MCP

by YeXuanHs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

re_strings

Extract crypto/Kirikiri strings with control-block signature offsets. Configure encoding, min length, keywords, and hit limits for reverse engineering/localization.

Instructions

Extract interesting crypto/Kirikiri strings (+ control-block signature offset).

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_strings"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
utf16No
min_lenNo
keywordsNo
max_hitsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

Without annotations, the description carries the full burden of behavioral disclosure. It states the core operation ('Extract') and hints at an extra output (control-block signature offset), but it does not explain the output format, how 'interesting' is determined, or any side effects or prerequisites. This is minimal coverage for an unannotated tool.

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, focused sentence that front-loads the main purpose with no redundant words. It is an efficient and well-structured summary.

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?

Despite having five parameters and no output schema or annotations, the description provides only a one-line overview. It omits return behavior, parameter details, and the meaning of 'interesting' or the offset, leaving significant gaps for an agent to correctly invoke the tool.

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

Parameters1/5

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

Schema coverage is 0%, and the description does not explain any of the five parameters (path, utf16, min_len, keywords, max_hits). The vague term 'interesting' might loosely relate to keywords, but it does not convey parameter semantics or constraints.

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?

The description clearly states the verb 'Extract' and the resource 'crypto/Kirikiri strings', making the tool's purpose specific and unambiguous. It also distinguishes itself from sibling tools by focusing on string extraction and mentioning the unique output of 'control-block signature offset'.

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?

No explicit guidance is provided on when to use this tool versus alternatives such as re_search or re_disasm. The mention of 'crypto/Kirikiri' implies a reverse-engineering context, but there are no named alternatives or exclusion criteria, so usage is only implied.

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