Skip to main content
Glama

pbi_create_measures

Batch create or update multiple DAX measures with validation via dry run. Use single SaveChanges call for efficient model updates.

Instructions

Batch-create or update multiple DAX measures with a single SaveChanges call.

Each item in measures must have at minimum: name, expression. Optional keys: format_string, description, display_folder, is_hidden.

With dry_run=True, every measure is name + expression validated and the per-item planned_action is reported (would_create/would_update/ would_fail), but no model mutation happens — SaveChanges is never called. Use this for an LLM preflight before committing the batch.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tableYes
dry_runNo
measuresYes
overwriteNo
stop_on_errorNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. Explains batch saving, optional keys, dry_run behavior (validation, planned_action reporting, no mutation). Does not detail error handling or output format, but covers core behavioral traits.

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 paragraphs, front-loaded purpose, then details options and dry_run. Efficiently structured with no wasted words.

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?

Complexity moderate (5 params, batch, dry_run). Covers main features but lacks output specification. Dry_run reports planned_action but no mention of success/error return format. Slightly incomplete given output schema exists but not detailed.

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 0%, so description must compensate. Explains measures (name, expression, optional keys) and dry_run. However, overwrite and stop_on_error parameters are not mentioned, leaving gaps.

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 'Batch-create or update multiple DAX measures with a single SaveChanges call', specifying the action (create/update), resource (DAX measures), and batch nature. Distinguishes from sibling pbi_create_measure (singular) by implying batching.

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?

Provides guidance on dry_run for preflight validation without mutation. Implies use for batch operations vs single measure tools. Lacks explicit when-not-to-use or alternatives for non-batch cases.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/imnotStealthy/powerbi-mcp-local'

If you have feedback or need assistance with the MCP directory API, please join our Discord server