Skip to main content
Glama

rename_measure

Rename a Power BI measure atomically across TMDL declarations, DAX formulas, and report visuals, with optional dry-run change planning and post-write validation.

Instructions

Atomically rename a measure across TMDL declarations, DAX formulas, and report visuals.

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": {
      "old_name": "<old_name>",
      "new_name": "<new_name>"
    },
    "name": "rename_measure"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose one real trait, atomicity across three artifact types, but omits whether the write is destructive or reversible, what happens on name collisions, and what validation or failure modes occur — details that matter for a multi-file mutation.

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?

One sentence, front-loaded with the verb and scope, with no filler wording. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists (the ChangePlan), so return values need no explanation, and all four parameters are documented. For an unannotated mutation tool, though, the description is thin on safety and failure semantics that an agent would want before executing a rename.

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 coverage is 100%, including a detailed dry_run description explaining default true behavior and post-write validation, so the schema does the heavy lifting. The description adds no parameter meaning beyond it, which is the baseline when coverage is high.

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 gives a specific verb (rename) plus the resource (measure) and the exact surfaces touched (TMDL declarations, DAX formulas, report visuals). That scope phrase also separates it from DAX-only siblings like update_measure_dax, though no sibling is named explicitly.

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 only implied: an agent can infer this is for renaming a measure everywhere at once. There is no stated when-to-use vs. update_measure_dax, no mention of preconditions such as looking up the name via search_measures, and no guidance on when a dry run is appropriate despite dry_run defaulting to true.

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