Skip to main content
Glama

plot

Render captioned PNG charts from tables or tensors—scatter, heatmaps, surfaces—to inspect high-dimensional data patterns.

Instructions

Render a PNG picture (returned as an image you can look at; also saved under HIDIM_OUT) with a one-line caption.

Tables: scatter (x,y[,z]; defaults to the first components of an embedding; color_by a label/cluster/numeric/datetime column, parent columns of an embedding work too: categories get a legend of up to 20 classes, numeric and datetime columns a colour bar; annotate= writes that column's value next to each point, up to 300 points), pairs (scatter matrix of <=6 features), parallel (parallel coordinates, min-max scaled), corr (correlation heatmap with feature labels, reordered by hierarchical clustering so correlated blocks are visible; order='given' keeps table order), heatmap (raw value matrix rows x columns), scree (PCA variance curve, auto scaling), hist (small-multiple histograms), andrews (Andrews curves by class). Tensors: tensor (heatmap of a 2-D slice), surface (3-D surface of a 2-D slice; numeric and datetime axes are drawn at their true values, log_axes=['maturity_days'] draws a dim on a log10 scale), lines (1-D slices over one dim, up to 12 series from series_dim; use select={'dim': {'isin': [...]}} to pick). Use select/reduce exactly as in slice_tensor to get down to 2 dims (or 1-2 for lines). Large tables are randomly sampled to HIDIM_PLOT_MAX_POINTS (20000) points; categorical colours beyond HIDIM_MAX_CLASSES (20) fold into 'Other'.

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": {
      "name": "<name>"
    },
    "name": "plot"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
zNo
kindNoscatter
nameYes
seedNo
orderNocluster
titleNo
widthNo
heightNo
reduceNo
sampleNo
selectNo
annotateNo
color_byNo
featuresNo
log_axesNo
log_colorNo
series_dimNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.6/5.0
Behavior5/5

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

With zero annotations the description carries the full burden and does so well: it discloses the output artifact (image returned AND written under HIDIM_OUT), the caption behavior, the downsampling rule ('randomly sampled to HIDIM_PLOT_MAX_POINTS (20000) points'), and the silent data-folding behavior ('categorical colours beyond HIDIM_MAX_CLASSES (20) fold into Other') plus the legend and annotation caps (20 classes, 300 points, 12 series). These are exactly the lossy-behavior traits an agent needs before trusting the rendered result.

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?

Front-loaded with the outcome (PNG + caption) before diving into kind-by-kind detail, and the 'Tables:'/'Tensors:' headers give it scannable structure. It is dense and parenthetical-heavy, but nearly every clause carries operational information rather than filler; only the nested parentheticals around color_by and surface make it harder to parse than it needs to be.

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?

For a 19-parameter, no-annotation, no-output-schema tool, this is close to complete: output form, storage location, sampling limits, class folding, per-kind constraints and select/reduce protocol are all covered, and the return-value explanation isn't needed since no output schema exists. The one real hole is that the sole required parameter `name` is never described, leaving the agent to infer it names the dataset to plot.

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 0%, so the description must compensate across 19 params, and it does for most: x/y/z defaults ('defaults to the first components of an embedding'), color_by accepts labels/clusters/numerics/datetimes with different legend vs colour-bar behavior, annotate, features, order ('given' keeps table order), log_axes with a concrete example, series_dim, select and reduce. Gaps remain: the required `name` parameter is never explained (presumably the dataset/table to plot), and seed, sample, width, height and title get no mention at all.

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?

Opens with a specific verb+resource: 'Render a PNG picture (returned as an image you can look at; also saved under HIDIM_OUT) with a one-line caption.' It then enumerates the eight table kinds and three tensor kinds, so an agent can tell exactly what this tool produces and which siblings (project, cluster, slice_tensor) it is not.

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?

The 'Tables:' vs 'Tensors:' split plus per-kind applicability notes (pairs <=6 features, lines needs 1-2 dims, heatmap needs a raw value matrix) effectively tell the agent which kind fits which data shape. It also defers to a sibling for setup semantics: 'Use select/reduce exactly as in slice_tensor to get down to 2 dims.' What's missing is explicit when-not guidance or a named alternative for cases where plotting is the wrong choice.

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