Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

inspect_solution_package

Read-only

Inspects local solution ZIP or base64 package without CRM setup, validating structure and reading solution.xml identity, publisher, and declaration counts without extraction or execution.

Instructions

Inspect a local solution ZIP or base64 without CRM configuration. Bounds ZIP headers, paths, inflated sizes and every payload CRC; reads only solution.xml identity, publisher and declaration counts. No extraction/execution. Does not prove authenticity, safe code, dependencies, contents or deployability.

Input Schema

NameRequiredDescriptionDefault
filePathNoAbsolute local file path. ZIPs are read without extraction or execution.
file_pathNoAbsolute local file path. ZIPs are read without extraction or execution.
contentBase64NoCanonical base64; ZIP bytes at most 32 MiB. Supply exactly one input source.
content_base64NoCanonical base64; ZIP bytes at most 32 MiB. Supply exactly one input source.
environment_profileNoOptional named environment profile for this call; omit to use the configured default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.2
    • addedInput schema / properties / environment_profile
      Added value: +{
      +  "description": "Optional named environment profile for this call; omit to use the configured default.",
      +  "pattern": "^[A-Za-z][A-Za-z0-9_]{0,31}$",
      +  "type": "string"
      +}
  2. First observedv1.0.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses important safety and behavior details: ZIP headers, paths, inflated sizes, and payload CRCs are bounded, and no extraction or execution occurs. It also lists what the inspection does not prove, which is valuable for setting agent expectations.

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 compact and front-loaded, starting with the core action and scope. Every sentence contributes either behavioral detail or a meaningful limitation, with no filler.

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?

For a read-only local package inspection tool with no output schema, the description sufficiently covers input sources, safety boundaries, what is read, and what is not validated. It gives enough context for an agent to invoke the tool correctly and interpret its limits.

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 the schema already documents filePath, contentBase64, and environment_profile. The description mentions local ZIP or base64 input but adds little parameter-level meaning beyond what the schema provides.

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 states a specific verb and resource: inspect a local solution ZIP or base64 package. It also scopes the operation clearly by saying it works without CRM configuration and reads only solution.xml identity, publisher, and declaration counts.

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 gives a clear usage context: local ZIP/base64 inspection without CRM configuration. It does not explicitly name sibling alternatives such as import_solution_async or verify_solution_deployment, so tool routing is implied rather than fully prescribed.

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