Skip to main content
Glama
Heretek-RE

re-il2cpp

by Heretek-RE

get_assembly_types

Enumerate every type in a Unity IL2CPP assembly by specifying the image name, returning full type definitions including fields, methods, and properties.

Instructions

Enumerate every type in one IL2CPP assembly.

Unlike :func:list_classes (which scans the string table and misses root-namespace types), this walks the typeDef range owned by a specific image — use it to enumerate the publisher's actual game code (Assembly-CSharp.dll) or a specific engine module (UnityEngine.CoreModule.dll).

Each record: {fqn, namespace, name, type_index, method_count, field_count, property_count, event_count, nested_type_count, parent_index, token, flags} — same shape as :func:get_type_definitions.

Args: metadata_path: path to global-metadata.dat image_name: assembly file name (e.g. "Assembly-CSharp.dll") limit: maximum results

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
metadata_pathYes
image_nameYes
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, but the description details that it walks the typeDef range owned by a specific image and lists the output fields. Lacks mention of side effects or permissions, but for a read-only query it is sufficient.

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 well-structured with bullet points and clear sections, no wasted words, and efficiently conveys all necessary information.

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?

Given no annotations and the presence of an output schema, the description is fairly complete: explains tool behavior, parameter semantics, and output shape. Could mention error conditions or required context, but adequate for the tool.

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

Parameters5/5

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

Schema description coverage is 0%, but the description explains the purpose of each parameter (metadata_path, image_name, limit) and the record structure, adding significant meaning beyond the schema.

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?

Clearly states it enumerates every type in one IL2CPP assembly, and explicitly distinguishes from list_classes which misses root-namespace types, making the purpose specific and distinct.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use guidance (enumerating publisher's code or engine module) and contrasts with list_classes, giving clear context and alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Heretek-RE/re-il2cpp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server