GraphMake

Get template fields

get_template

Read-onlyIdempotent

Read one template: its size, description and every editable text and number, as field keys with their current values (e.g. "w0.text": "Annual Report 2026", "w5.datasets.0.values": [820, 1050]). Copy the keys you want to change into render_template. Set preview to true to also get the template's preview image.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Template id from list_templates.
`preview`	No	Also return the template preview image (default false).

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`name`	Yes
`width`	Yes	Canvas width in px.
`fields`	Yes	Every editable text and number. Send changed values to render_template by key.
`height`	Yes	Canvas height in px.
`category`	Yes
`previewUrl`	Yes	The template preview image.
`description`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "category": {
+      "enum": [
+        "business",
+        "education",
+        "marketing",
+        "health",
+        "technology",
+        "general"
+      ],
+      "type": "string"
+    },
+    "description": {
+      "type": "string"
+    },
+    "fields": {
+      "description": "Every editable text and number. Send changed values to render_template by key.",
+      "items": {
+        "properties": {
+          "key": {
+            "description": "Field key, e.g. \"w0.text\" or \"w5.datasets.0.values\".",
+            "type": "string"
+          },
+          "value": {
+            "description": "Current value: text, a number, or a list."
+          },
+          "widget": {
+            "description": "The widget type the field belongs to.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "key",
+          "widget",
+          "value"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "height": {
+      "description": "Canvas height in px.",
+      "type": "integer"
+    },
+    "id": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "previewUrl": {
+      "description": "The template preview image.",
+      "type": "string"
+    },
+    "width": {
+      "description": "Canvas width in px.",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "category",
+    "width",
+    "height",
+    "description",
+    "previewUrl",
+    "fields"
+  ],
+  "type": "object"
+}

First observedOct 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: it describes the returned field-key/value structure and the side effect of preview=true (extra preview image), which the annotations do not convey.

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 compact sentences, front-loaded with what is returned, followed by the actionable next step and the optional preview flag. Every clause earns its place; no filler.

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 two-parameter read tool with an output schema already present, the description supplies everything needed: the resource, id provenance, the return structure with examples, and the two downstream uses (render_template, preview). Nothing required to 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 description coverage is 100%, so the baseline is 3, but the description adds the key-format example that tells an agent how the returned keys map back to render_template inputs, and it reinforces the preview flag's meaning. That is meaningful guidance beyond the schema text.

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 (Read) and resource (one template) and enumerates exactly what is returned: size, description, and editable text/number field keys with values. The example keys ("w0.text", "w5.datasets.0.values") make the output shape concrete and separate it from list_templates (enumeration) and render_template (mutation).

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?

Gives a clear follow-on workflow: copy the keys you want to change into render_template, and set preview to true to also fetch the preview image. It does not state when-not to use it (e.g. vs list_templates for discovery), but the read-vs-render split is inferable from the named sibling.

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?