Dataverse MCP Server

dataverse_list_plugin_steps

Read-onlyIdempotent

List SDK message processing steps registered in the environment.

Instructions

List SDK message processing steps registered in the environment.

Use plugin_type_id to scope to one plug-in type, or message_id to scope to one message. Results ordered by name ascending.

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": {
      "params": "<params>"
    },
    "name": "dataverse_list_plugin_steps"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.6.0Jul 15, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds ordering behavior ('Results ordered by name ascending') and scoping options, but does not disclose whether results are paginated or if specific permissions are required. Given annotation coverage, this is adequate but not rich.

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 concise: two sentences, 33 words. It front-loads the purpose in the first sentence and adds details in the second. No redundant phrases or wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has an output schema (covering return values) and good annotations, the description covers purpose, scoping, and ordering. It omits mentioning pagination (though 'top' parameter exists) but is otherwise complete for a list operation.

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?

The input schema has high coverage with descriptions for each parameter (e.g., 'top', 'filter', 'plugin_type_id'). The tool description adds that results are ordered by name ascending, which is not in the schema. With schema coverage high, baseline is 3, and the addition provides marginal extra value.

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 'List SDK message processing steps registered in the environment.' It uses a specific verb ('List') and resource ('SDK message processing steps'), and distinguishes from siblings like dataverse_get_plugin_step (singular) and other list tools.

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

Usage Guidelines4/5

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

The description provides guidance on when to use: 'Use plugin_type_id to scope to one plug-in type, or message_id to scope to one message.' It also mentions ordering. However, it does not explicitly state when not to use it or contrast with alternatives like get_plugin_step for a single step.

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

Deploy Server