Skip to main content
Glama

Bar Chart Race Maker

create_bar_chart_race
Read-onlyIdempotent

Prefill the Bar Chart Race Maker: an animated bar chart from a table or CSV, where bars grow, shrink and overtake each other. Returns a link that opens the Tool with these options; the user presses Export there to download the video. All options are optional. Icons and images that need a file upload are not supported.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_bar_chart_race"
  }
}

Input Schema

NameRequiredDescriptionDefault
bgNoBackground color. Default: "#ffffff".
cxNoHorizontal offset of the chart in pixels. Default: 0.
cyNoVertical offset of the chart in pixels. Default: 0.
decNoDecimal places shown in the values. Default: "0".
durNoTotal seconds of the race. Default: 10.
endNoSeconds the final frame holds at the end. Default: 1.
fpsNoExport frame rate. Default: "30".
palNoColor palette of the bars. Default: "vivid".
preNoText before each value, such as $. Default: "".
resNoExport resolution. Default: "720".
sepNoThousands separator of the values. Default: "comma".
sufNoText after each value, such as %. Default: "".
barsNoHow many bars are shown at once. Default: 8.
fontNoFont id of the chart text. Default: "inter".
holdNoSeconds each step of the race holds before the next. Default: 0.
sizeNoVideo size (aspect ratio) preset. Default: "16:9".
colorNoColor of the text. Default: "#111827".
titleNoChart title text. Default: "Most used video editors".
salignNoAlignment of the step label. Default: "right".
splaceNoWhether the step label sits above (up) or below (down) the chart. Default: "down".
talignNoAlignment of the title. Default: "left".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, non-destructive, idempotent operation. The description adds meaningful behavior beyond annotations: it only prefills options, returns a link, and requires the user to press Export in the opened Tool; it also discloses the limitation around upload-dependent icons/images.

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?

The description is three tight sentences, front-loads the purpose and result, then clarifies the export workflow and an important limitation. Every sentence contributes useful information with no redundant wording.

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?

For a tool with 21 fully documented optional parameters and existing safety annotations, the description covers purpose, return behavior, user follow-up action, and a notable unsupported case. It is nearly complete, though it could mention whether the returned link is persistent or session-bound.

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 description coverage is 100%, so the input schema already documents all 21 parameters, defaults, enums, and constraints. The description adds only that all options are optional and that upload-dependent assets are not supported, without adding per-parameter meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action and resource: 'Prefill the Bar Chart Race Maker' and explains it produces an animated bar chart from a table or CSV. This clearly distinguishes it from generic chart creation, though it does not explicitly compare against sibling animation tools.

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?

It explains the resulting workflow: a link opens the Tool and the user presses Export there to download the video, and it notes that file-upload icons/images are unsupported. However, it does not explicitly say when to choose this over sibling animation makers or state other exclusions/preconditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.