Skip to main content
Glama

update_measure_dax

Update a measure's DAX expression in TMDL while preserving surrounding formatting, with a dry-run option to preview the proposed change before writing files.

Instructions

Update a measure's DAX expression in TMDL while preserving surrounding formatting.

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": {
      "measure_name": "<measure_name>",
      "expression": "<expression>"
    },
    "name": "update_measure_dax"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableNoOptional table name to disambiguate the measure.
dry_runNoWhen true, return the proposed ChangePlan without modifying files. Defaults to true. Set false to execute the write with post-write validation.
workspaceNoWorkspace identifier returned by list_workspaces (prefer workspace_id or unique name). Optional when the server is bound to a single workspace.
expressionYesReplacement DAX expression.
measure_nameYesExact measure name to update.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden; it implies a mutation and adds the useful guarantee that surrounding formatting is preserved. It does not itself disclose the dry-run-by-default workflow, execution condition, or post-write validation, although the input schema documents those behaviors.

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 single sentence is front-loaded with the action and target, then ends with a meaningful formatting guarantee. It contains no filler or redundant explanation.

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 fully described five-parameter schema and presence of an output schema, the definition supplies enough combined information for correct invocation, including targeting, dry-run behavior, and validation. The terse description remains adequate but would be more complete with explicit usage routing and clearer mutation-safety context.

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 the baseline score of 3 applies. The description reinforces the roles of measure_name and expression but adds no parameter syntax, naming, or disambiguation details beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: updating a measure's DAX expression in TMDL. Limiting the change to the expression and promising preservation of surrounding formatting clarifies scope, although no sibling tool or explicit boundary is named.

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

Usage Guidelines3/5

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

Usage is implied for expression-only measure updates where surrounding TMDL formatting should remain intact. There is no explicit when-to-use, when-not-to-use, prerequisite, or routing guidance versus tools such as format_dax or rename_measure.

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