Dataverse MCP Server

dataverse_get_environment_variable_values

Read-onlyIdempotent

Get environment variable value records in Dataverse by value ID, definition GUID, or variable name, returning consistent list results.

Instructions

Get environment variable value record(s).

Provide exactly one targeting path:

value_id: fetch a single value record by its own GUID directly.
definition_id: list value record(s) linked to the given definition GUID.
name: resolve the definition by schema name or display name, then list its value record(s). Schema name is tried first; display name is the fallback.

Returns a list shape (records, count, has_more) in all cases for a consistent calling convention, even when a single record is expected. When no value record exists for a definition the list will be empty.

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_get_environment_variable_values"
  }
}

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.4/5.0

Behavior4/5

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

Annotations already declare the tool as read-only and idempotent. The description adds important behavioral details: the return shape is always a list with records/count/has_more, even for single records, and describes behavior when no records exist. It also explains name resolution priority, providing transparency beyond annotations.

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 well-structured: a one-line purpose, a bullet-like list of targeting paths, and a short note on return shape. Every sentence adds value, with no redundancy or fluff.

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 presence of a comprehensive input schema and output schema, the description adequately covers usage scenarios, return shape, and edge cases (empty list). It could be improved by mentioning that the tool only retrieves values for a single definition at a time, but overall it is complete.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already provides descriptions for all parameters, including mutual exclusivity. The description adds value by explaining the order of name resolution (schema name first, then display name) and consolidating the targeting paths. With high schema coverage, the baseline is 3, and the additional context justifies a 4.

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 purpose as retrieving environment variable value records, and distinguishes it from the sibling tool dataverse_get_environment_variables which retrieves definitions. It specifies three targeting paths, making the action and resource unambiguous.

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 explicitly states that exactly one targeting path must be provided, outlines each path's use case, and notes the consistent return shape. However, it does not explicitly state when not to use this tool or compare it to alternatives beyond the sibling name, which prevents a perfect score.

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

Deploy Server