Skip to main content
Glama

GraphMake

by com.graphmake
OverviewDiscussionsAdmin

Render infographic

render_infographic
Read-onlyIdempotent

Render GraphMake Script into an infographic image (PNG or SVG). GraphMake Script is a simple line-based syntax: title "...", kpi "Label" "Value" icon=users, bar_chart "T" { Jan: 42\n Feb: 68 }, timeline { 2024: "Event" "detail" }, style bold, row { ... } for side-by-side blocks, and more. Call graphmake_script_reference first if you have not seen the full syntax. Returns the image and a link that opens it in the GraphMake editor for hand-editing and export. Parse errors name the line, so fix the script and call again.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
widthNoOptional canvas width in px (max 4000).
formatNopng (default) returns an image; svg returns the SVG markup as text, ready to save to a file.
heightNoOptional canvas height in px (max 8000).
scriptYesThe GraphMake Script to render.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
bytesYesSize of the PNG or SVG in bytes. The image itself is in the content.
formatYes
editorUrlYesOpens the result in the free GraphMake editor, where it can be restyled and exported as PNG, SVG or PDF.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "bytes": {
+      "description": "Size of the PNG or SVG in bytes. The image itself is in the content.",
+      "type": "integer"
+    },
+    "editorUrl": {
+      "description": "Opens the result in the free GraphMake editor, where it can be restyled and exported as PNG, SVG or PDF.",
+      "type": "string"
+    },
+    "format": {
+      "enum": [
+        "png",
+        "svg"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "format",
+    "bytes",
+    "editorUrl"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent, not open-world), and the description adds real behavior beyond them: it returns the image plus an editor link, and parse errors name the offending line so the agent knows retries are expected. It does not mention limits or costs, but the added retry/return context is substantive.

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 core action, then syntax examples and the recovery loop. The syntax examples are dense but each earns its place by making the required `script` parameter usable; no filler sentences.

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 an output schema present, return values need not be detailed, yet the description still summarizes the return (image + editor link). For a 4-param tool with full schema coverage and annotations, nothing an agent needs to call 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 width/height/format are already documented, and the description still adds value by illustrating the opaque `script` string syntax with concrete examples. That compensates for the fact that the schema only says 'The GraphMake Script to render'.

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?

States a specific verb (render) and resource (GraphMake Script → infographic image) with output formats named. It is clearly distinguishable from the render_template sibling because it operates on raw script rather than templates.

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?

Explicitly instructs 'Call graphmake_script_reference first if you have not seen the full syntax,' giving a clear prerequisite and follow-up loop on parse errors. It lacks an explicit when-to-use-this-vs-render_template comparison, but the input type makes the distinction clear.

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

All GraphMake 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