Dataverse Plugin MCP

Overview Schema Source Related Servers Discussions Admin

delete_package

Delete a registered Dataverse plugin package (Nuget) along with its assemblies, plug-in classes, and steps. Use when you need to remove an entire package from the environment.

Instructions

Delete a registered PluginPackage (Nuget package).

WARNING: this also deletes every assembly, plug-in class, and step inside the package.

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": {
      "package_name_or_id": "<package_name_or_id>"
    },
    "name": "delete_package"
  }
}

Input Schema

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

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 for behavioral disclosure. It discloses a critical side effect: deleting the package also deletes every assembly, plug-in class, and step. It does not mention permissions or reversibility, but the cascade warning is highly valuable and directly addresses the main risk.

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 long, with the critical warning front-loaded and no filler. Every sentence adds value: the first states the core action, the second highlights the cascading deletion.

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 description covers the most important contextual point (destructive cascade) and leverages the output schema for return values. However, it lacks guidance on when to use this tool versus sibling delete tools and does not mention the optional environment parameter's role. For a destructive operation, one might expect more context on prerequisites or consequences, but the warning mitigates this.

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 0%, so the description must compensate. The description does not explain the parameters at all. The parameter names 'package_name_or_id' and 'environment' are somewhat self-explanatory, but no additional meaning is provided beyond the schema fields.

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') and the specific resource ('a registered PluginPackage (Nuget package)'). This distinguishes it from sibling tools like delete_assembly and delete_step, which target lower-level components.

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 the tool is used to delete a full package but does not explicitly contrast it with alternatives (e.g., 'use delete_assembly to remove a single assembly'). No when-to-use or when-not-to-use guidance is provided.

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