Skip to main content
Glama

Inspect Managed Artifact

inspect_managed_artifact
Idempotent

Inspect a managed PE/CLI artifact or the selected target without loading or executing code, returning identity, classification, dependencies, and coverage details for safe metadata review.

Instructions

Inspect an explicit PE/CLI path, or the selected managed target, without loading or executing target code. Omitted or complete detail returns complete metadata inventories with original coverage. Select detail: "summary" on the first call for complete identity, PE/CLI, classification with its evidence, module/MVID, assembly, frameworks, returned-collection counts, coverage/issues and limitations. It retains complete Evidence and returns a distinct linked inspect_analysis_view summary. Page original references/resources/attributes with view kind managed and normalized_result.parent_evidence_id. Counts cover producer-returned rows; partial, unavailable or malformed metadata remains explicit and tokens remain build-local.

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": {
      "path": "/tmp/Example.dll"
    },
    "name": "inspect_managed_artifact"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoExplicit absolute managed PE/CLI path; omit to reuse the previously selected managed target
detailNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare idempotent, non-destructive, closed-world behavior, so the description does not need to restate safety. It adds genuinely useful behavior beyond them: the no-execution guarantee, that partial/unavailable/malformed metadata is surfaced explicitly rather than silently dropped, and that counts reflect 'producer-returned rows' with 'original coverage'. What is missing is any statement on permissions or cost of repeated calls, so it is not a 5.

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 purpose is front-loaded, which is good, but the remainder is a dense run-on stack of clauses with unexplained internal terms ('build-local', 'normalized_result.parent_evidence_id', 'MVID'). Several ideas (coverage semantics, paging instructions, error behavior) are compressed into one sentence each rather than structured, which forces re-reading.

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?

There is no output schema, and the description does partially cover the return shape (metadata inventories, evidence, coverage/issues/limitations, collection counts), which is appropriate for a complex inspection tool. But it leans on concepts defined elsewhere — 'linked inspect_analysis_view summary', 'build-local' tokens, view-kind paging — without explaining them, so an agent unfamiliar with the sibling's model cannot fully predict the response.

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?

With schema coverage at 50%, the description carries real weight: it explains that omitting 'path' reuses the previously selected managed target, and it defines what 'complete' versus 'summary' detail returns. The one gap is that the schema enum also allows 'full', which the description never distinguishes from 'complete', leaving an agent to guess between two enum values that the schema presents as separate.

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 first sentence names a specific verb and two accepted targets ('explicit PE/CLI path, or the selected managed target') and adds a key constraint ('without loading or executing target code'). It is distinguishable from sibling inspectors by its managed-assembly focus and by naming the linked inspect_analysis_view. It stops short of a 5 because the density of jargon (MVID, build-local tokens, normalized_result.parent_evidence_id) makes the core purpose slower to grasp than it should be.

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?

It does give one concrete usage instruction — 'Select detail: "summary" on the first call' — and explains how to page references via 'view kind managed and normalized_result.parent_evidence_id'. However, it never states when to prefer this over siblings such as inspect_managed_members, inspect_artifact, or inspect_managed_native_boundaries, nor when omission of 'path' is inappropriate. Guidance is implied rather than enumerated.

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