Dataverse MCP Server

dataverse_get_choice

Read-onlyIdempotent

Get one GLOBAL choice (option set) — all option values, codes, and labels — by name or MetadataId.

Instructions

Get one GLOBAL choice (option set) — all option values, codes, and labels — by name or MetadataId.

For the options of a specific column's LOCAL choice use dataverse_list_choice_column_options instead. Provide either name or metadata_id; name takes precedence when both are given.

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

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

Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, destructiveHint. Description adds value by clarifying global vs. local scope, precedence behavior, and that it returns all options. No contradictions found.

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?

Two sentences, no filler. Each sentence serves a distinct purpose: stating functionality and providing usage guidance with alternative. Highly efficient.

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?

Output schema exists, so return values need no explanation. Description covers core functionality, parameter usage, and distinguishes from siblings. Missing mention of consistency_strong and dataverse_url, but these are in schema. Complete enough for an agent to use correctly.

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?

Schema description coverage is 0%, so description must compensate. Description mentions 'by name or MetadataId' and precedence rule, covering two of four parameters. Does not address dataverse_url or consistency_strong, though schema descriptions fill part of the gap. Partial compensation earns baseline 3.

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?

Description clearly states 'Get one GLOBAL choice (option set) — all option values, codes, and labels — by name or MetadataId.' It uses specific verb and resource, and distinguishes from sibling dataverse_list_choice_column_options by contrasting GLOBAL vs LOCAL.

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?

Explicitly states when to use alternative tool: 'For the options of a specific column's LOCAL choice use dataverse_list_choice_column_options instead.' Provides precedence rule for name over metadata_id. Lacks broader context like prerequisites but offers clear decision guidance.

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

Deploy Server