Skip to main content
Glama
rededis

dataverse-mcp-server

by rededis

update_attribute

Modify metadata of an existing Dataverse column: display name, description, required level, length, min/max values, precision, and DateTime options. Type and logical name cannot change.

Instructions

Update metadata of an existing column: display name, description, required level, max length, min/max value, precision. Dataverse fixes a column's type and logical name at creation — to change either, add_attribute a new column, migrate the values with update_record, then delete_attribute the old one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesCurrent type of the attribute (required to build the correct metadata discriminator; must match the existing type — type changes are not allowed)
requiredNoNew required level
max_valueNoNew max value (numeric types only)
min_valueNoNew min value (numeric types only)
precisionNoNew precision (Decimal/Money only)
max_lengthNoNew max length (String/Memo only)
date_formatNoDateTime only: change UI presentation. See add_attribute for semantics.
descriptionNoNew description
display_nameNoNew display name
merge_labelsNoIf true, preserve existing localized labels in other languages; if false (default), replace all localized labels with just the new one.
date_behaviorNoDateTime only: change storage semantics. ONE-WAY per Microsoft — you can switch from UserLocal to DateOnly or TimeZoneIndependent once, but cannot switch back or between the non-UserLocal values. Dataverse will return 400 if the behavior is already locked.
language_codeNoLanguage code for labels (default: 1033)
entity_logical_nameYesLogical name of the entity
attribute_logical_nameYesLogical name of the column to update

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv0.5.0

TDQS

A4.4/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, and it discloses real constraints: type/logical-name immutability and the Dataverse migration path. It stops short of stating whether unspecified fields are left unchanged, permission/auth requirements, or reversibility of other edits, so it is strong but not exhaustive.

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, zero padding: the mutable-field summary is front-loaded and the immutability/migration caveat follows. Every clause earns its place.

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?

For a 14-parameter mutation tool with no annotations and no output schema, the description plus rich schema covers the essentials — what can change, what cannot, and the workaround. Missing only operational context like auth requirements and post-update behavior.

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 100%, so every parameter is already documented in the schema, including enums and the one-way date_behavior lock. The description's field list merely restates those parameters and adds no syntax or format detail beyond them.

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?

States a specific verb (Update) and resource (metadata of an existing column) and enumerates the mutable fields, immediately distinguishing it from add_attribute and delete_attribute.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states what cannot be done (type and logical name are fixed at creation) and supplies the exact alternative workflow — add_attribute, migrate with update_record, then delete_attribute. An agent knows both when to use this and when to route elsewhere.

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