Dataverse Plugin MCP

by lucasjesus0311

Overview Schema Source Related Servers Discussions Admin

Python

Local

list_images

Identify pre/post images attached to an SDK message processing step in Dataverse using its step ID.

Instructions

List the pre/post images registered on an 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>"
    },
    "name": "list_images"
  }
}

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

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only operation via 'List' but does not state side effects, authentication needs, pagination, or behavior when the step does not exist. This falls short for a tool with no annotation support.

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, focused sentence with no filler. It is appropriately concise for a simple list operation and every word adds value.

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?

Despite having an output schema, the description is incomplete given the lack of annotations and parameter semantics. The role of environment in filtering or selecting the step is absent, and no usage context is provided. This would leave an agent uncertain about correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/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. It mentions the step concept but does not explain the step_id parameter or the optional environment parameter at all. The schema only gives names, and the description adds no clarifying meaning.

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 tool's action: 'List the pre/post images registered on an SDK message processing step.' It specifies the resource (pre/post images) and the scope (a step), distinguishing it from sibling list tools like list_registered_plugins or list_environments.

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 given for when to use this tool versus alternatives, prerequisites, or exclusions. The only implied context is that it involves a step, but there is no explicit mention of environment selection or relationship to sibling tools.

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