Skip to main content
Glama
mafaq229

pbirb-mcp

by mafaq229
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

insert_tablix_from_template

Build a basic Tablix in a Power BI report by specifying columns, dataset, and layout dimensions. Each column creates a header and data-bound detail row.

Instructions

Build and append a basic Tablix to /. One column per name in columns; header row gets the column name as a static label, detail row binds to =Fields!.Value. dataset_name must already exist. width is the tablix outer width — each column defaults to 1in regardless, so for a 3-column tablix the columns sum to 3in even if you pass width=10cm. Resize columns afterwards via direct edits or future column-width tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topYes
leftYes
nameYes
pathYes
widthYes
heightYes
columnsYes
dataset_nameYes

Tool Definition Quality

A3.8/5.0
Behavior4/5

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

No annotations present, so description bears full responsibility. It discloses the append behavior, dataset requirement, width behavior (columns default to 1in regardless of width), and need for post-hoc column resizing. It does not mention destructive potential, but appending is non-destructive. Overall, it provides good behavioral insight beyond the basic action.

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?

Description is concise at ~70 words, front-loading the main purpose. It uses clear examples and straightforward language. Minor improvement could be structuring into bullet points or separate sentences for readability, but current form is acceptable without 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?

Given 8 required parameters and no output schema, the description covers the critical aspects (columns, dataset_name, width) but omits explanation of `path`, `top`, `left`, `height`, and `name`. It also does not clarify the return value or side effects. It is adequate for simple scenarios but leaves gaps for new users.

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. It explains `columns` (list of column names), `dataset_name` (must exist), and `width` (outer width, columns not scaled). However, it does not describe `top`, `left`, `height`, `path`, or `name`. It adds significant meaning for some params but leaves others unclear.

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 the tool builds and appends a basic Tablix to <Body>/<ReportItems> with header and detail rows. It explains the column structure (static labels, Field! bindings) and distinguishes from column-width tools, though not explicitly from siblings. The verb 'Build and append' is specific and the resource is clear.

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?

Description mentions prerequisite that dataset_name must exist and hints at column-width tools for resizing, but does not explicitly state when to use this tool versus alternatives like add_tablix_column or other add_* tools. No 'when not to use' guidance is provided.

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/mafaq229/pbirb-mcp'

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