Skip to main content
Glama

GraphMake

by com.graphmake
OverviewDiscussionsAdmin

Render template

render_template
Read-onlyIdempotent

Render a template filled with new content. "changes" maps the template's field keys to new values, e.g. {"w0.text": "Q3 Sales Review", "w5.labels": ["Jul","Aug","Sep"], "w5.datasets.0.values": [42, 51, 63]}. Fields not included keep the template's sample content. Replacing a whole list (e.g. "w7.values": [{"label": "A", "value": 40}, ...]) changes how many items it has; each item keeps the colours of the item it replaces. Returns the image and a link that opens the filled template in the GraphMake editor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTemplate id, e.g. "business-stats".
formatNopng (default) returns an image; svg returns the SVG markup as text.
changesNoField key -> new value, e.g. {"w0.text": "Q3 Sales Review"}.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
nameYes
bytesYesSize of the PNG or SVG in bytes. The image itself is in the content.
widthYesWidth of the returned image in px (tall templates come back narrower).
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. Changed2 schema fields changed
    • changedInput schema / properties / changes / description
      Previous value: -"Field key -> new value, keys from get_template."New value: +"Field key -> new value, e.g. {\"w0.text\": \"Q3 Sales Review\"}."
    • changedInput schema / properties / id / description
      Previous value: -"Template id from list_templates."New value: +"Template id, e.g. \"business-stats\"."
  2. 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"
+    },
+    "id": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "width": {
+      "description": "Width of the returned image in px (tall templates come back narrower).",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "format",
+    "bytes",
+    "width",
+    "editorUrl"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Despite annotations already declaring readOnly/idempotent/openWorld, the description adds substantial behavioral context: unspecified fields retain sample content, replacing a list changes item count, each item inherits the replaced item's colours, and the response includes both an image and an editor link.

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 examples that earn their place by disambiguating the nested 'changes' format. Slightly dense with inline JSON but 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?

Given the output schema exists and annotations cover the safety profile, the description covers the remaining burden: how 'changes' is structured, the preservation default, list-replacement semantics, and what comes back. Nothing essential to a correct call 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 the baseline is 3, but the description goes further by giving concrete 'changes' key syntax (dotted paths like "w5.datasets.0.values", JSON arrays) and by noting that omitted keys are preserved — meaning well beyond what the schema's terse 'Field key -> new value' line conveys.

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?

States a specific verb+resource ('Render a template filled with new content') and immediately clarifies what 'changes' means. It does not, however, differentiate itself from the sibling render_infographic or explain which rendering tool an agent should pick.

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?

Usage is implied by the description — you render a template by supplying its id and field changes — but there is no explicit when-to-use vs when-to-use-an-alternative guidance, and no mention of prerequisites such as first calling list_templates or get_template to discover ids/field keys.

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