Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

d365_plugin_steps_query

Read-only

Query native Dynamics 365 plugin steps using exact filters such as message, entity, stage, mode, and step ID; Secure Configuration is excluded unless explicitly included.

Instructions

Query native plugin steps with exact filters. Secure Configuration is excluded by default; explicit include_secure_configuration=true is required to read plaintext. All supplied filters, including step_id, are combined. Results are bounded by top.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
topNoMaximum results; default 50.
modeNo0/Synchronous or 1/Asynchronous. Async requires PostOperation.
stageNo10/PreValidation, 20/PreOperation, 40/PostOperation.
stepIdNoCompatibility alias for step_id. Conflicting aliases are rejected.
enabledNo
messageNoExact SDK message name, for example Update.
step_idNo
assemblyNameNoCompatibility alias for assembly_name. Conflicting aliases are rejected.
assembly_nameNoExact assembly name to disambiguate a plugin class.
primaryEntityNoCompatibility alias for primary_entity. Conflicting aliases are rejected.
pluginTypeNameNoCompatibility alias for plugin_type_name. Conflicting aliases are rejected.
primary_entityNoLogical table name. Omit for a global message registration.
plugin_type_nameNoExact plugin class name, such as Company.Plugins.AccountUpdate.
environment_profileNoOptional named environment profile for this call; omit to use the configured default.
includeSecureConfigurationNoCompatibility alias for include_secure_configuration. Conflicting aliases are rejected.
includeUnsecureConfigurationNoCompatibility alias for include_unsecure_configuration. Conflicting aliases are rejected.
include_secure_configurationNoExplicit opt-in to read and return Secure Configuration plaintext. Default false, changed from the legacy package.
include_unsecure_configurationNoInclude Unsecure Configuration in query results, default true (legacy behavior).

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.1/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation, the description discloses a genuinely important behavior the schema alone would not emphasize: Secure Configuration plaintext is excluded by default and requires explicit opt-in. It also clarifies conjunctive filter semantics and top-bounded results. It stops short of describing returned fields or how omitted filters behave (match-all vs. error).

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?

Three short sentences, each carrying distinct information: purpose, the sensitive-data default, and filter/result semantics. The security default is front-loaded ahead of the mechanics, and there is no filler or repetition.

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 an 18-parameter, zero-required, read-only query tool with no output schema, the description covers the non-obvious risks (sensitive config exposure, filter conjunction, result bounds). What remains unstated — which fields come back and what an empty filter set returns — is modest, since the schema already documents defaults for the include_* flags.

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?

Schema coverage is already 89%, so the schema carries most parameter documentation. The description adds meaning the schema does not: that all supplied filters, including step_id, are combined rather than ORed or prioritized, and that top bounds the result set. This is real added semantics on top of an already well-documented 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?

"Query native plugin steps with exact filters" states a specific verb (query) and resource (plugin steps), plus a scope qualifier (exact-match filters) that separates it from a broad listing or metadata introspection tool. It does not name the neighboring registration/update siblings, so the differentiation is implicit rather than explicit.

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 usable operating context: filters are ANDed together, results are capped by top, and Secure Configuration is withheld unless explicitly opted in. It does not tell the agent when to reach for d365_plugin_registration_metadata or the assembly-level query tools instead, so alternative selection is left to inference.

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