Skip to main content
Glama

pbi_parameterize_data_source

Replace hardcoded file paths in Power BI data sources with a parameter, enabling collaborators to change the file location from Manage parameters dialog without editing queries.

Instructions

Make data sources portable via a Power Query parameter.

Creates (or updates) an M parameter named parameter_name whose default value is file_path. Then rewrites every M partition that string-matches file_path so it calls File.Contents(<parameter_name>) instead of the hardcoded path. After the parameter is wired in, a collaborator can change the file location once via Power BI Desktop's Transform data → Manage parameters dialog without editing each query.

partitions: optional explicit list of "Table[/Partition]" to rewrite. By default every M-source partition that references file_path is rewritten.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runNo
file_pathYes
partitionsNo
refresh_afterNo
parameter_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries full burden. It explains the core behavior (creates/updates parameter, rewrites partitions) and default behavior for 'partitions' but does not discuss side effects, reversibility, or the effects of 'dry_run' and 'refresh_after'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with two paragraphs, no fluff, and front-loaded with the main purpose and workflow. It could be more structured but is efficient.

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

Completeness2/5

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

With 5 parameters and an output schema existing, the description only explains 2 parameters, ignores 'dry_run' and 'refresh_after', and does not mention prerequisites (e.g., connection) or side effects. It is incomplete for a tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%. The description adds meaning for 'parameter_name' and 'file_path' implicitly, and explains 'partitions' thoroughly, but 'dry_run' and 'refresh_after' are not described at all. Only 2 of 5 parameters get sufficient explanation.

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?

The description clearly states the tool's purpose: making data sources portable via a Power Query parameter. It uses specific verbs ('parameterize', 'rewrites', 'wires in') and distinguishes from siblings by focusing on parameterization for portability rather than direct relocation.

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?

The description explains the benefit (collaborators can change file location via Manage parameters) but does not explicitly contrast with alternatives like 'pbi_relocate_data_source'. It implies usage for hardcoded paths but lacks when-not-to-use guidance.

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