Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

d365_plugin_images_query

Read-only

List native plugin images for an exact Dynamics 365 step without reading plugin configuration, with bounded results that report completeness and do not follow continuation links.

Instructions

List native images for an exact step without reading plugin configuration. Bounded results report completeness; does not follow continuation links.

Input Schema

NameRequiredDescriptionDefault
topNo
stepIdNo
step_idNo
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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description does add real behavioral detail beyond that: results are bounded and report their own completeness, and continuation links are not followed, so the agent knows to check for truncation rather than paginate. It stops short of saying how completeness is signaled or what the bound is.

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?

Two short sentences, front-loaded with the action and scope, with no filler. The 'without reading plugin configuration' clause is slightly oblique and costs a little clarity for its brevity.

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?

With no output schema, the description would ideally indicate what an image record contains (assembly, class, alias, image type, attributes), and it does not. Pagination/truncation behavior is covered, but the meaning of the 'top' bound and the exactness requirement on step_id are left implicit.

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 coverage is only 25%, with just environment_profile documented, so the description should carry more weight here. 'Exact step' usefully implies step_id must be a precise identifier rather than a name or partial match, but top, the step_id/stepId alias, and the required-either-of behavior go unaddressed.

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 states a specific verb and resource ('List native images') scoped to 'an exact step', which separates it from the mutating siblings d365_plugin_image_register/update/delete. It does not explicitly contrast with the closest read siblings (d365_plugin_steps_query, d365_plugin_registration_metadata), so sibling differentiation is only partial.

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?

'without reading plugin configuration' implies the tool exists as a lighter-weight alternative to pulling full plugin registration configuration, which is usable context. However, no sibling is named, there are no explicit exclusions ('use X instead when...'), and nothing states the precondition that the step must already exist.

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