Skip to main content
Glama
mafaq229

pbirb-mcp

by mafaq229
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

add_body_textbox

Add a textbox to the report body that accepts static text or RDL expressions. Ensures unique names and coexists with existing tablix.

Instructions

Add a Textbox to /. text accepts static strings or RDL expressions (e.g. =Globals!ReportName). Coexists with the existing tablix; rejects names already in use. Pass raw text — encoding is handled; don't pre-encode XML entities (use & not &, including for the VB.NET string-concat operator in expressions).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topYes
leftYes
nameYes
pathYes
textYesStatic text or RDL expression (=...).
widthYes
heightYes

Tool Definition Quality

A3.6/5.0
Behavior4/5

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

Given no annotations, the description usefully discloses that duplicate names are rejected and encoding is handled, giving the agent key behavioral expectations.

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?

Three concise sentences efficiently convey essential information without redundancy; the first sentence front-loads the purpose.

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?

Without annotations or output schema, the description is insufficient: it omits crucial details like parameter units (top/left/width/height), the meaning of 'path', and name constraints, leaving the agent underinformed.

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 only 14%; the description adds value only for the 'text' parameter (encoding detail), but 6 out of 7 parameters (path, name, top, left, width, height) lack any additional semantics in either schema or description.

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 action 'Add a Textbox' and the precise location '<Body>/<ReportItems>', which effectively differentiates it from sibling tools like add_header_textbox or add_footer_textbox.

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 provides some usage guidance (handling of expressions, duplicate names, encoding) but does not explicitly contrast with alternatives or specify conditions for use.

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