Dataverse Plugin MCP

by lucasjesus0311

Overview Schema Source Related Servers Discussions Admin

Python

Local

list_steps

Lists the SDK message processing steps for a plug-in, detailing the message, entity, and stage.

Instructions

List the SDK message processing steps (message/entity/stage) of a plug-in class.

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": {
      "plugin_type_name_or_id": "<plugin_type_name_or_id>"
    },
    "name": "list_steps"
  }
}

Input Schema

Name	Required	Description	Default
`environment`	No
`plugin_type_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

B3.4/5.0

Behavior3/5

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

With no annotations available, the description carries the burden of behavioral disclosure. The verb 'List' implies read-only behavior, but it does not explicitly state that no modifications occur, nor does it mention permissions, environment dependencies, or return format. Basic but not rich context.

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, front-loaded sentence that efficiently conveys the purpose without unnecessary words. It earns its place with clear verb and object.

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 an output schema, so return values are covered. However, the description omits context about the environment parameter, any prerequisites for using the tool, and how it fits into the broader workflow of managing steps. It is adequate for a simple list tool but lacks important operational details.

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%, and the description does not explain the parameters. The phrase 'of a plug-in class' maps to plugin_type_name_or_id, but it provides no detail about the environment parameter or how to specify the plugin. The description adds minimal meaning beyond the parameter names.

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 specific verb ('List') and the resource ('SDK message processing steps (message/entity/stage) of a plug-in class'). It differentiates from sibling tools like create_step/update_step/delete_step by indicating a read-only list operation and clarifies the scope to a plug-in class.

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, such as before creating or updating steps. It does not mention prerequisites like selecting an environment or the need for the plugin to exist.

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