Skip to main content
Glama

Inspect Managed Members

inspect_managed_members
Idempotent

Inspect managed PE/CLI metadata members, signatures, CIL hashes, call edges, and field accesses without loading or executing code; filter by exact type names to limit large assemblies.

Instructions

Inspect PE/CLI metadata members, signatures, raw CIL hashes, decoded-instruction-tuple hashes, separately reported exception regions, call edges, and field-access anchors without loading or executing target code. Select type_names to decode only the members of those exact declaring types, which keeps large assemblies such as a base class library within the representation budget. Metadata tokens are reported as build-local coordinates bound to the artifact SHA-256 and MVID; the tuple hash does not resolve them or fully commit control flow.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "inspect_managed_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoExplicit absolute managed PE/CLI path; omit to reuse the previously selected managed target
type_namesNoInspect only the fields, methods, call edges, and field accesses declared by these exact type full names; omit to inspect every type. Unmatched names are reported in selection.unmatched_type_names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behavioral constraints: it does not load or execute target code, type filtering keeps large assemblies within a representation budget, metadata tokens are build-local coordinates bound to artifact SHA-256 and MVID, and tuple hashes do not resolve tokens or fully commit control flow. These caveats materially affect how an agent should interpret and trust the results.

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 dense but front-loaded: the first sentence defines the inspection scope, the second explains the main filtering parameter, and the third states token/hash limitations. Every sentence contributes useful technical context, though the long enumeration in the first sentence makes it less immediately readable.

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?

For a complex metadata-inspection tool with no output schema, the description covers the main data categories and critical interpretation caveats, and the input schema fully documents parameters. It still does not describe the result structure, pagination or representation limits, or failure behavior, so it is strong but not fully complete.

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%, so both parameters are already fully documented in the schema, including exact declaring-type matching and omission/reuse behavior. The description mostly reinforces the same semantics and adds the rationale that type_names keeps large assemblies within the representation budget, but it does not add substantial syntax or selection details beyond the schema.

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?

The description gives a specific verb and resource: inspecting PE/CLI metadata members, and enumerates the exact artifacts covered (signatures, hashes, exception regions, call edges, field-access anchors). It implicitly separates this from runtime or comparison tools by emphasizing metadata inspection without loading or executing target code, but it does not explicitly distinguish itself from siblings such as compare_managed_members.

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?

Usage guidance is implied through parameter behavior: use type_names to limit decoding to exact declaring types, and omit path to reuse the previously selected target. There is no explicit when-to-use statement, no exclusions, and no named alternative telling an agent when to choose this tool instead of related inspection or comparison tools.

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