Skip to main content
Glama

create_lollipop_chart

Create ranked lollipop charts to compare numeric values across categories, with optional highlighting of a specific entity for clear top-N lists or budget comparisons.

Instructions

Lollipop chart — dots on stems for clean ranking. Can highlight one entity.

Ideal for: district population ranking, budget by ministry, top-N lists.

Returns: {filepath, title, rows}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesRow dicts
themeNoVisual themedark
titleNoChart title
filenameNoOutput filenamelollipop_chart
label_columnYesCategory labels
value_columnYesNumeric values to rank by
highlight_valueNoValue to highlight (e.g., 'Grad Beograd')
highlight_columnNoColumn to match for highlighting

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations provided; description adds return format and highlighting capability but lacks details on sorting, missing values, or default behavior. Adequate but not comprehensive.

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?

Extremely concise, three sentences with no fluff. Front-loaded with purpose and use cases.

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?

Given 8 parameters, full schema coverage, and existence of output schema, the description provides enough context for a straightforward chart tool. Could mention sorting or ranking order but not essential.

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 covers all 8 parameters with descriptions. Tool description adds minimal value beyond the schema, only explaining the highlight feature. Baseline 3 is appropriate.

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 creates a lollipop chart for ranking, with examples like district population ranking. It distinguishes from sibling chart tools by specifying the chart type and use case.

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?

Lists ideal use cases (ranking, top-N lists), which guides when to use. Does not explicitly exclude alternatives but gives clear context.

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/acailic/serbian-data-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server