Skip to main content
Glama
Sign In
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

plan_form_solution_package

Read-only

Reads source and target main forms and previews adding the entire source form to an existing unmanaged solution; references are not automatically added or fully analyzed.

Instructions

Read source and target main forms and preview adding the entire source form to an existing unmanaged solution. References are not automatically added or fully analyzed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "source_profile": "<source_profile>",
      "target_profile": "<target_profile>",
      "logical_name": "<logical_name>",
      "source_form_id": "<source_form_id>",
      "target_form_id": "<target_form_id>",
      "solution_unique_name": "<solution_unique_name>"
    },
    "name": "plan_form_solution_package"
  }
}

Input Schema

NameRequiredDescriptionDefault
logical_nameYes
source_form_idYes
source_profileYes
target_form_idYes
target_profileYes
environment_profileNoOptional named environment profile for this call; omit to use the configured default.
solution_unique_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

B3.4/5.0
Behavior4/5

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

The description adds useful behavioral context beyond the readOnlyHint annotation: it previews the addition and warns that references are not automatically added or fully analyzed. It does not contradict the read-only annotation, since 'preview adding' is a planning action rather than an actual mutation.

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 two sentences, front-loaded with the core action and followed by a relevant caveat. It contains no redundant or filler wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with seven parameters, six required, low schema coverage, and no output schema, the description is too sparse. It does not explain the required identifiers, what the preview returns, or how the source and target profiles are meant to be used.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 14%, so the description must compensate for six undocumented required parameters, but it does not. It loosely references source and target forms and an existing unmanaged solution, yet gives no meaning for logical_name, source_form_id, target_form_id, solution_unique_name, or the profile parameters.

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 action: read source and target forms and preview adding an entire source form to an existing unmanaged solution. The word 'preview' distinguishes it from a mutating apply operation, though it does not explicitly name or contrast with siblings such as apply_form_solution_package or inspect_form_solution_package.

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?

The description implies this is a planning/preview step before applying a form solution package, but it does not explicitly say when to use this versus apply_form_solution_package or inspect_form_solution_package. No when-not or prerequisite guidance is provided.

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