Dataverse Plugin MCP

Overview Schema Source Related Servers Discussions Admin

configure_tracing

Enable or disable Dataverse plug-in trace logging by setting the level to Off, Exception, or All. Use it to diagnose plug-ins, then switch back to conserve storage.

Instructions

Turn the environment's Plug-in Trace Log on/off (required for list_execution_logs to work).

level: 'Off', 'Exception' (only logs when the plug-in throws an exception), or 'All' (always logs). Remember to switch back to 'Off' or 'Exception' after debugging -- logs consume the organization's storage space.

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": {
      "level": "<level>"
    },
    "name": "configure_tracing"
  }
}

Input Schema

Name	Required	Description	Default
`level`	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.1/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that logs consume storage and recommends returning to a lower level after debugging, which are meaningful behavioral traits. It does not mention side effects on the environment or return output, but the core operational behavior is transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description opens with a clear one-sentence purpose, then provides level definitions and a storage warning. It is somewhat lengthy but each part earns its place; the multi-line format is acceptable for the extra context.

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?

The description covers purpose, when to use, level semantics, and a key consequence (storage usage). With an output schema present and sibling tools providing environment selection context, it is mostly complete. Missing details are the meaning of the optional environment parameter and the return value, but these are minor gaps.

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 schema provides 0% coverage for parameter meaning. The description fills in the 'level' parameter thoroughly by enumerating 'Off', 'Exception', and 'All' with definitions. However, the 'environment' parameter is not explained at all, which leaves a gap for a 2-param tool.

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 states 'Turn the environment's Plug-in Trace Log on/off' which is a specific verb+resource action. It also immediately notes 'required for list_execution_logs to work', helping differentiate this tool from sibling tools that perform logging or execution-related tasks.

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 gives clear context: this tool must be enabled before list_execution_logs will function. It also advises switching back to 'Off' or 'Exception' after debugging, implying when not to keep it on. However, it does not explicitly name alternatives or state when to use each level beyond the basic definitions.

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