Skip to main content
Glama
mafaq229

pbirb-mcp

by mafaq229
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

set_body_item_position

Move a named ReportItem inside to new top and left coordinates. Preserves size, style, and group structure. Supports units like cm, in, pt.

Instructions

Move an existing named ReportItem inside to (top, left). Preserves all other properties (size, style, group structure). top and left are passed through verbatim — RDL accepts any size unit (2cm, 0.75in, 108pt). Errors if no body item by that name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topYes
leftYes
nameYes
pathYes

Tool Definition Quality

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that properties are preserved, top/left accept any RDL size unit, and an error occurs if the item doesn't exist. It does not mention transaction requirements, return values, or auth, but the disclosed traits are useful and accurate.

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?

Three sentences, front-loaded with purpose, then details, then error condition. No wasted words. Efficient and clear.

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

Completeness4/5

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

The description is nearly complete given the 4 parameters, no output schema, and no annotations. It covers purpose, key parameter behavior, and an error condition. Missing explicit path explanation and behavioral context like transaction state, but overall adequate.

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 top, left (any unit), and name (existing item in Body). However, the 'path' parameter is not explained; its role is only implied by 'inside <Body>'. Partial coverage of the 4 parameters.

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 verb 'move' and the resource 'existing named ReportItem inside <Body>' to target coordinates. It distinguishes from sibling tools like set_body_item_size and add_body_image by specifying it changes position while preserving other properties.

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?

The description implies when to use (move without altering size/style) but does not explicitly state when not to use or name alternatives. The sibling set_body_item_size is implicitly distinguished by the phrase 'preserves all other properties'. Somewhat clear but not fully explicit.

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