Skip to main content
Glama
Heretek-RE

re-dotnet

by Heretek-RE
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

parse_assembly

Parse a .NET assembly to extract header metadata and a summary of all types, including namespace, visibility, and member counts. Quick first-step analysis for .NET binaries.

Instructions

Enumerate TypeDef rows in path.

Returns the assembly header (name, version, target framework, entry point) plus a one-row-per-type summary. This is the .NET cousin of re-lief.parse_binary and re-il2cpp .get_assembly_types — the analyst's first call on a .NET-style launcher or mod-loader.

Output shape::

{
  "header": {
    "path": "...",
    "assembly_name": "...",
    "assembly_version": "...",
    "target_framework": "...",
    "corlib": "...",
    "is_mixed_mode": bool,
    "entry_point": "Namespace.Type::Method",
    "file_kind": "assembly" | "netmodule",
    "type_count": N,
    "method_count": N,
    "field_count": N,
  },
  "types": [
    {"fqn": "...", "namespace": "...", "name": "...",
     "is_public": bool, "method_count": N, "field_count": N,
     "property_count": N, "event_count": N, "nested_type_count": N,
     "base_type": "..."},
    ...
  ],
  "truncated": false
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes

Tool Definition Quality

A4.4/5.0
Behavior5/5

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

With no annotations provided, the description fully discloses the tool's behavior by detailing the output structure, including fields like 'truncated' flag. It implies a read-only enumeration without modification, and the shape of the return value is comprehensively described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear action first, then a detailed output specification. It is concise for the amount of information provided, though the code block could be considered lengthy.

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

Completeness5/5

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

Given the tool has a single parameter and no output schema, the description provides a complete understanding of usage and output. It includes comparative context with other tools, meeting all needs for this simple 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?

The single parameter 'path' is only cursorily mentioned ('in *path*') without explanation of its meaning or format. With 0% schema description coverage, the description should provide more context, such as that it expects a file path or assembly location.

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 action ('Enumerate TypeDef rows in *path*') and specifies the resource (assembly file). It distinguishes from siblings by noting it's the 'first call' for .NET-style launcher or mod-loader, and compares to external tools like re-lief.parse_binary and re-il2cpp.get_assembly_types.

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

Usage Guidelines4/5

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

The description implies usage as an initial step for .NET binaries ('analyst's first call'), providing context for when to use it. However, it lacks explicit guidance on when not to use it or direct alternatives among the listed sibling tools, though the comparison to external tools partially compensates.

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-dotnet'

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