Skip to main content
Glama
Sign In
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

review_component_three_way

Read-only

Compares caller-supplied baseline, source, and target file contents using whole-file hashes to report concurrent changes without merging, packaging, or authorizing release.

Instructions

Compare caller-supplied baseline, source and target text contents using whole-file hashes. Reports concurrent changes; does not merge, package or authorize release.

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": {
      "name": "<name>",
      "baseline": "<baseline>",
      "source": "<source>",
      "target": "<target>"
    },
    "name": "review_component_three_way"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
sourceYes
targetYes
baselineYes
environment_profileNoOptional named environment profile for this call; omit to use the configured default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

A3.7/5.0
Behavior4/5

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

readOnlyHint=true is already declared, so the bar is lower, and the description still adds real context: comparison is hash-based at whole-file granularity (not a line diff), it reports concurrent changes, and it performs no merge, packaging, or authorization. Those explicit non-actions tell the agent what side effects to expect from the follow-up calls.

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?

Two tight sentences with the comparison mechanism and the excluded behaviors front-loaded; nothing is redundant with the title or the annotations.

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?

For a read-only, five-parameter tool with no output schema, the description should sketch what the report contains (per-file match/mismatch? conflict list?), and it does not. It is adequate on scope and safety but leaves the agent guessing about the result shape and the unexplained 'name' parameter.

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 only 20%, so the description must compensate, and it partly does: it names baseline, source and target and clarifies they are 'caller-supplied' text rather than server-fetched artifacts. The required 'name' parameter and the meaning of a whole-file hash mismatch are left 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?

States a specific verb ('Compare') and resource ('component') with the three inputs named, and 'whole-file hashes' pins down the comparison granularity. It is clearly distinct from review_form_three_way by resource, though it never names that sibling explicitly.

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?

Usage is implied rather than stated: the agent learns this is a pre-release review step because it 'does not merge, package or authorize release.' There is no positive trigger ('call before apply_form_solution_package') and no routing to review_form_three_way, compare_environment_forms, or verify_form_baseline for adjacent jobs.

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