Skip to main content
Glama
mafaq229

pbirb-mcp

by mafaq229
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

list_body_items

List all top-level ReportItems in a paginated report's body, returning their name, type, and dimensions. Useful to inspect before modifying item positions or sizes.

Instructions

List every named ReportItem at the top level of . Returns name, type (Tablix / Textbox / Image / Rectangle / Subreport / Chart / etc.), top, left, width, height. Use before set_body_item_position / set_body_item_size when you don't already know what's in the body.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute path to the .rdl file to read.

Tool Definition Quality

A4.5/5.0
Behavior4/5

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

Despite no annotations, description clearly indicates a read-only listing operation with no side effects. It could mention behavior for empty body or invalid paths, but it is transparent enough for a simple listing tool.

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, no fluff, front-loaded with purpose. Each sentence adds value: first lists output, second provides usage guidance.

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

Completeness5/5

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

Given no output schema, description adequately explains return fields. For a simple tool with one parameter, it covers essential context without missing critical information.

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% with a single 'path' parameter documented as 'Absolute path to the .rdl file to read.' Description adds no additional meaning beyond the schema, meeting baseline expectation.

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 specifies verb 'list', resource 'ReportItem at the top level of <Body>', and what is returned (name, type, dimensions). It clearly distinguishes from sibling tools by mentioning usage before set_body_item_position/set_body_item_size.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use: 'before set_body_item_position / set_body_item_size when you don't already know what's in the body.' This provides clear context and alternative tools.

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