GraphMake

List templates

list_templates

Read-onlyIdempotent

List GraphMake's designed infographic templates (id, name, category, size, what it is for). Pass a query such as "sales report", "timeline", "resume" or "comparison" to rank the best matches first. Then call get_template with an id.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	No	Optional words describing the infographic you need.
`category`	No	Optional category filter.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`templates`	Yes	Best match first when a query was given.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "templates": {
+      "description": "Best match first when a query was given.",
+      "items": {
+        "properties": {
+          "category": {
+            "enum": [
+              "business",
+              "education",
+              "marketing",
+              "health",
+              "technology",
+              "general"
+            ],
+            "type": "string"
+          },
+          "description": {
+            "type": "string"
+          },
+          "height": {
+            "description": "Canvas height in px.",
+            "type": "integer"
+          },
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "width": {
+            "description": "Canvas width in px.",
+            "type": "integer"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "category",
+          "width",
+          "height",
+          "description"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "templates"
+  ],
+  "type": "object"
+}

First observedOct 2, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and a closed-world scope, so the safety profile is covered. The description adds the ranking behavior of the query parameter, which is useful, but says nothing about result counts, pagination, or what happens when no query/category is supplied.

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 short sentences, front-loaded with purpose and returned fields, then usage and the follow-up call. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, parameter usage and the workflow handoff to get_template; an output schema exists so return values need no explanation. Only minor gaps remain around result volume and default behavior when no filter is passed.

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 concrete query examples ("sales report", "timeline", "resume", "comparison") go beyond the schema's generic "words describing the infographic you need" and clarify the expected vocabulary and the ranking effect.

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?

Specific verb (List) plus resource (GraphMake infographic templates) and an explicit inventory of what each result contains (id, name, category, size, purpose). It is immediately distinguishable from get_template, which the description names as the follow-up single-item call.

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 clear context (pass a query to rank matches first) and routes to the sibling get_template with an id for the next step. It stops short of stating when NOT to use it (e.g., browsing everything with no query), so it is strong but not exhaustive.

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?