Skip to main content
Glama

add_line

Add a line to report items by specifying start coordinates and vector. Optionally set color, thickness, and line style.

Instructions

Add a to /. RDL Line semantics: top/left is the start point; width/height is the offset (vector) to the end point — horizontal line uses height='0in', vertical uses width='0in'. Optional color, line_thickness ('1pt' default), line_style (Solid/Dashed/Dotted/Double/etc.). Returns {name, kind: 'Line'}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topYes
leftYes
nameYes
pathYes
colorNo
widthYes
heightYes
line_styleNo
line_thicknessNo
Behavior4/5

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

With no annotations, description provides key behavioral details: coordinate interpretation, optional styling parameters, and return structure. Lacks disclosure of error conditions or permission requirements, but sufficient for a simple add operation.

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, no extraneous content. Front-loaded with purpose, followed by critical coordinate semantics and optional parameters. Efficient.

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?

Covers purpose, coordinate system, optional parameters, and return value. Lacks details on path existence validation or error handling, but adequate given tool's simplicity. No output schema, so return info is helpful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage, but description adds substantial meaning: explains top/left/width/height as start+offset, line_thickness default, line_style enum, and return shape. This goes far beyond the raw schema.

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?

Clearly states action ('Add a <Line>'), target resource ('<Body>/<ReportItems>'), and distinguishes from siblings like add_body_image or add_body_textbox by specifying the line element. Includes coordinate semantics and optional parameters.

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?

Describes coordinate system (top/left as start, width/height as offset) which aids correct usage, but does not explicitly state when to use this tool over alternatives like add_rectangle, nor mention prerequisites or restrictions.

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