GraphMake

Open in GraphMake editor

open_in_editor

Read-onlyIdempotent

Build a GraphMake editor URL that opens with the script already rendered on the canvas, for when the user wants to hand-edit, restyle or export the infographic.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`script`	Yes	The GraphMake Script to load.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`editorUrl`	Yes	Opens 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.

Changed1 schema field changedOct 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "editorUrl": {
+      "description": "Opens the result in the free GraphMake editor, where it can be restyled and exported as PNG, SVG or PDF.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "editorUrl"
+  ],
+  "type": "object"
+}

First observedOct 2, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and idempotentHint=true, so the safety and idempotency profile is covered structurally. The description adds meaningful context: the URL opens with the script already rendered on the canvas, implying a stateful hand-editing session. It does not mention whether the URL expires or requires authentication, but given the annotations, this is a solid addition.

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?

A single, well-structured sentence that front-loads the action ('Build a GraphMake editor URL') and then explains the resulting state and use case. Every clause earns its place with no redundancy.

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?

The tool is simple (one parameter, no nesting) and has an output schema, so the description does not need to explain return values. It fully covers the purpose and the user-facing scenario for invoking the tool, leaving no critical gaps for an agent to call it correctly.

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 coverage is 100% and the single parameter 'script' is fully documented in the schema. The description does not add any new semantic information about the parameter beyond what is already in the schema, which is the expected baseline when the schema is comprehensive.

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 ('Build a GraphMake editor URL') and resource, and clarifies the exact purpose — opening with the script rendered on the canvas. It is clearly distinguishable from siblings like render_infographic and render_template, which produce output rather than a hand-editable editor session.

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?

Provides a clear usage context — 'for when the user wants to hand-edit, restyle or export the infographic.' However, it does not explicitly contrast with the closest alternative (render_infographic) or state when this tool should not be used (e.g., when the user wants a final rendered image).

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

All GraphMake tools Inspect

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

Need Help?