Skip to main content
Glama

insert_chart_from_template

Insert a column chart into a Power BI Report Builder .rdl report using an existing dataset, specifying category and value fields, position, and size.

Instructions

Build and append a basic Column chart to /. Single category axis grouped by category_field; single Y series Sum(Fields!.Value). dataset_name must already exist. Change post-insert (e.g. to Bar / Line / Pie) by editing the chart directly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topYes
leftYes
nameYes
pathYes
widthYes
heightYes
value_fieldYes
dataset_nameYes
category_fieldYes
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the chart is appended, uses Sum aggregation, and can be modified post-insert. However, it does not mention error behavior, idempotency, or side effects (e.g., overwriting). The description is adequate but not thorough.

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 sentences that are front-loaded and concise. Every sentence adds value: purpose, structure, and a tip for post-insert modification. 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?

Given 9 required parameters, no output schema, and no annotations, the description covers the core behavior but lacks details on parameter semantics and return values. It partially differentiates from siblings but is not fully complete for confident tool selection.

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 coverage is 0%, so the description must compensate. Only 3 of 9 parameters (dataset_name, category_field, value_field) are described. Parameters like top, left, path, name, width, height are not explained, leaving significant ambiguity for the agent.

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 it builds and appends a basic Column chart to <Body>/<ReportItems>, specifying the chart structure (single category axis grouped by category_field, single Y series with Sum aggregation). It is distinct from siblings like add_chart_series or set_chart_series_type, which modify existing charts.

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 clear context: the chart is a Column chart by default, dataset_name must exist, and type can be changed post-insert. However, it does not explicitly state when not to use this tool vs. alternatives like add_chart_series or set_chart_series_type.

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