Dataverse Plugin MCP

Overview Schema Source Related Servers Discussions Admin

toggle_step

Enable or disable a Dataverse SDK message processing step to manage plugin execution without deleting and recreating the step.

Instructions

Enable or disable an existing SDK message processing step.

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>",
      "enabled": "<enabled>"
    },
    "name": "toggle_step"
  }
}

Input Schema

Name	Required	Description	Default
`enabled`	Yes
`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

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the binary toggle. It fails to mention side effects, whether the step must already exist, idempotency, permission requirements, or the outcome of toggling a nonexistent step. This is insufficient for a mutation tool.

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 a single concise sentence with no redundant wording. It front-loads the action and clearly identifies the resource. While it could contain more detail, the existing structure is efficient and contains no filler.

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?

The tool is a mutation with 3 parameters and no annotations. The description is too terse to provide enough operational context. It fails to clarify how environment is used, when to use this over update_step, or what happens after toggling. The presence of an output schema does not compensate for missing usage and parameter context.

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 descriptions are absent (0% coverage), and the description does not explain step_id, enabled, or environment. The phrase 'enable or disable' clarifies the 'enabled' boolean, but step_id and especially environment semantics are left undefined, forcing the agent to infer from the parameter name only.

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 (enable or disable) and the resource (existing SDK message processing step). The word 'existing' distinguishes it from step creation tools, and the binary toggle action effectively differentiates it from create/update/delete step tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like update_step. It does not mention prerequisites (e.g., listing steps to obtain step_id) or how the environment parameter affects selection. There are no exclusions or alternative tool references.

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