Skip to main content
Glama
Sign In
Universal Game Modder

Universal Game Modder

by doritoman90000
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

analyze_dll_structure

Inspect a DLL's sections, imports, and exports to map its structure and spot dependencies before patching or modding game binaries.

Instructions

Analyze the overall structure of a DLL: sections, imports, exports summary.

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": {
      "file_path": "<file_path>"
    },
    "name": "analyze_dll_structure"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesPath to DLL file

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 discloses the inspection categories (sections, imports, exports), which is useful, but says nothing about read-only safety, failure on non-DLL input, size limits, or output form. Partial behavioral coverage only.

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 the verb and resource first, followed by the inspected artifacts. No filler or redundancy.

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?

With no output schema and no annotations, the description is the only disclosure channel, yet it does not describe the return shape or error behavior. The scope enumeration (sections, imports, exports) is the minimum needed to call it, but the definition is not complete for a binary-analysis tool.

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 description coverage is 100% for the single file_path parameter, so the schema already documents the input. The description adds no format, path-resolution, or validation detail beyond it, making the baseline 3 appropriate.

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?

States a specific verb+resource ('Analyze the overall structure of a DLL') and enumerates what is inspected (sections, imports, exports summary), so the agent knows exactly what it produces. However, it does not distinguish itself from overlapping siblings like analyze_pe_full or extract_dll_classes, which also inspect binary structure.

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 reference to alternatives such as analyze_pe_full or analyze_file_format, even though several siblings analyze binaries. The agent is left to infer when this tool is the right choice.

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