Skip to main content
Glama
Sign In

ChartAnt

by net.chartant
OverviewDiscussionsAdmin

KPI cards

generate_kpi_card
Read-onlyIdempotent

Draw 1 to 4 KPI cards as one image: each a big number with its label, optional change since the last period (green when good, red when bad) and an optional sparkline of recent values. For report emails, Slack updates and dashboards in documents. To combine KPI cards with charts in one image use generate_dashboard. Returns a hosted PNG link, a share page, alt text and editable PowerPoint/Excel links.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "items": "<items>"
    },
    "name": "generate_kpi_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesOne to four cards, left to right.
titleNoHeading above the cards, e.g. 'This week'.
brandThemeNoName of a brand theme saved on the user's account (their colours and footer), only when the user asks for their theme. Or "colorblind" for colours that people with colour-vision deficiency can tell apart (anyone can use it).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, non-destructive generation call, and the description adds the output shape beyond them: hosted PNG link, share page, alt text, and editable PowerPoint/Excel links. It does not mention generation cost, latency, or theme prerequisites, but with annotations covering the safety profile, the added return-format detail is substantial.

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 the visual output, then usage, then the sibling routing and return values. No filler; every sentence carries selection or invocation-relevant information.

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

Completeness5/5

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

With only 3 parameters, a fully described schema, and no output schema, the description covers the remaining gaps: what the image contains, when to use it, the alternative, and what the caller receives. Nothing needed to select or invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds meaning beyond it by explaining the good/bad colour semantics ('green when good, red when bad'), which clarifies how goodWhen and delta interact visually. It also reinforces the 1-to-4 card bound, though remaining detail (prefix, unit, caption, brandTheme) is left to the 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?

Names a specific verb and resource ('Draw 1 to 4 KPI cards as one image') and spells out exactly what each card contains: a big number, optional delta, optional sparkline. It also names the sibling it is not (generate_dashboard), so an agent can distinguish it without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete use cases (report emails, Slack updates, dashboards in documents) and an explicit routing rule: use generate_dashboard to combine KPI cards with charts. The alternative and the condition that selects it are both stated.

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

All ChartAnt toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources