Skip to main content
Glama

get_methods

Retrieve the list of methods for a specified type in a .NET or Mono assembly, including signatures and access modifiers.

Instructions

List the methods of one type (Mono / .NET pure assembly).

Pure routing: the C# CLI already implements list-methods in :mod:Re.Dotnet.Cli.Ops.MetadataOps (uses System.Reflection.Metadata via the .NET 10 runtime). This MCP wrapper is the v2.8.1 (A12) addition that exposes the Mono path the r03-stress run flagged as missing.

A12 note (v2.8.0): on Mono assemblies (e.g. CD's MonoLauncher) this tool did not exist; callers had to fall back to decompile_type + regex on the C# source. The MCP wrapper fixes the routing gap; the underlying CLI subcommand is already battle-tested on the IL2CPP path (re-il2cpp.get_methods uses the same code path).

Args: path: path to a .dll / .exe .NET or Mono assembly fqn: fully-qualified type name (e.g. MyGame.PlayerController) limit: max rows to return (default 500)

Returns::

{"path": "...", "fqn": "...", "type_fqn": "...",
 "count": N,
 "methods": [{"name": "...", "signature": "...",
              "is_public": bool, "is_static": bool,
              "is_virtual": bool, "is_abstract": bool,
              "is_final": bool, "is_special_name": bool,
              "rva": N, "token": "..."}, ...]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
fqnYes
limitNo
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that the tool returns a list of methods with detailed attributes and is a wrapper around a CLI subcommand. No destructive behavior implied.

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

Conciseness3/5

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

The description includes background context (A12 note, Mono path) that is informative but somewhat verbose. It is structured with sections (description, args, returns) but could be more concise.

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 output schema, the description provides a detailed return format. It also explains the tool's purpose, parameter details, and development context, making it sufficiently complete for an agent.

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

Parameters4/5

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

All three parameters (path, fqn, limit) are explained with descriptions and default value for limit. This compensates for 0% schema description coverage.

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 tool's purpose: listing methods of a type in Mono or .NET assemblies. It distinguishes from sibling tools like decompile_type and get_fields.

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?

Provides context on when to use this tool (e.g., for Mono assemblies, fixing a routing gap) and mentions an alternative fallback (decompile_type + regex). Lacks explicit when-not-to-use but offers clear guidance.

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