Dataverse Plugin MCP

Overview Schema Source Related Servers Discussions Admin

set_secure_configuration

Set or update a plug-in step's secure configuration, storing text accessible only to the plug-in and hidden from the UI. Creates the record if missing, or updates the existing one.

Instructions

Set the Secure Configuration of a step (text only accessible to the plug-in, not shown in the PRT/UI).

Creates the secure configuration record if the step doesn't have one yet, or updates the existing one.

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>",
      "value": "<value>"
    },
    "name": "set_secure_configuration"
  }
}

Input Schema

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

A4/5.0

Behavior4/5

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

With no annotations, the description carries the transparency burden. It discloses the upsert behavior (creates or updates) and the key fact that the value is not shown in the PRT/UI, which is valuable context. However, it does not mention permissions, error handling, or side effects, leaving some gaps.

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 and front-loaded: the first sentence states the core purpose, and the second explains the create/update behavior. It consists of two sentences with no filler or redundancy.

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 main purpose and a key behavioral trait (hidden from UI), which is adequate for a simple upsert tool. Yet with no annotations and a 0% parameter coverage, it leaves the environment parameter and return values unexplained. Overall it is minimally viable but not rich.

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 should compensate by explaining the parameters. It only indirectly implies step_id and value through the sentence 'Set the Secure Configuration of a step', and it does not mention the optional environment parameter at all. This is insufficient for an agent to construct proper calls.

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 sets the Secure Configuration of a step, with a specific verb and resource. It further distinguishes the tool by explaining that the data is hidden from the PRT/UI, setting it apart from general step update 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 conveys when to use the tool: when setting a step's secure configuration. It does not explicitly name alternatives, but the unique 'secure configuration' scope makes the intended context clear enough. It also clarifies the create-or-update behavior, which helps the agent know it's safe to call regardless of whether a record exists.

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