Dataverse Plugin MCP

Overview Schema Source Related Servers Discussions Admin

delete_step

Delete an SDK message processing step to remove its images in cascade and stop plug-in execution for that message, entity, and stage combination.

Instructions

Delete an SDK message processing step (its images are removed in cascade).

WARNING: the plug-in stops executing for this message/entity/stage combination.

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": {
      "step_id": "<step_id>"
    },
    "name": "delete_step"
  }
}

Input Schema

Name	Required	Description	Default
`step_id`	Yes
`environment`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 1, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and discloses two critical behaviors: cascade deletion of images and the permanent stop of plugin execution. This goes beyond a simple 'delete' statement and warns of irreversible side effects. It lacks details on authorization or recovery, but the core transparency is strong.

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, front-loaded with the main action, and uses a separate WARNING line for the critical consequence. Both sentences are necessary and serve distinct roles, making it highly concise and well-structured.

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?

The tool has a minimal schema and no annotations, but the description covers the main action and a major side effect. It falls short on explaining the environment parameter and does not mention alternative flows like toggle_step. Given an output schema is present, return values are likely covered, but the overall context has gaps.

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 coverage is 0% and the description does not mention any parameters. step_id is inferable from context, but the optional environment parameter is undefined, leaving ambiguity about its purpose and necessity. The description adds no value beyond the schema's minimal titles.

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 clearly states the action: 'Delete an SDK message processing step' with a specific verb and resource. It also distinguishes from siblings like delete_image and delete_assembly by noting the cascade removal of images, making the purpose unambiguous.

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 provides a clear consequence (plug-in stops executing), which implies this is a permanent deletion, but it does not explicitly mention alternatives like toggle_step for temporary disablement. There is context about the impact, but no explicit when-not-to-use or sibling comparison.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.