Skip to main content
Glama

mdmagic-mcp-server

by io.github.MDMagic-MCP

list_builtin_templates

Read-onlyIdempotent

List the 15 built-in MDMagic templates, grouped by category. Same as list_all_templates but excludes the user's custom uploads. Use this when the user asks specifically about MDMagic's bundled templates rather than their personal ones.

Categories available: Business (5), Creative (6), Professional (2), Technical (2).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoOptional filter — return only templates in this category.
includeDetailsNoInclude template details like available page sizes and orientations (default: false)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "count": {
-      "description": "Number of templates returned",
-      "type": "integer"
-    },
-    "templates": {
-      "description": "Matching built-in templates",
-      "items": {
-        "properties": {
-          "category": {
-            "description": "Category label (built-in templates only)",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "description": {
-            "description": "Short description of the template's intended use",
-            "type": "string"
-          },
-          "id": {
-            "description": "Template ID — pass this as templateName to convert_document",
-            "type": "string"
-          },
-          "name": {
-            "description": "Human-readable template name",
-            "type": "string"
-          },
-          "type": {
-            "description": "Source of the template",
-            "enum": [
-              "built-in",
-              "custom"
-            ],
-            "type": "string"
-          }
-        },
-        "required": [
-          "id",
-          "name",
-          "type"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "templates"
-  ],
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint:false, so the safety profile is covered. The description adds concrete behavioral facts: exactly 15 templates, grouped by category, and exclusion of custom uploads. This exceeds the annotation baseline without contradicting it.

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?

The description is three concise sentences plus a compact category list. It front-loads the core purpose and differentiation, and every sentence earns its place—no filler or 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?

For a simple read-only list tool, the combination of description, schema, and annotations fully covers what the tool does, when to use it, its parameters, and its safety profile. No output schema exists, but for a template listing the return shape is evident.

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. The description adds value by listing the categories with counts (Business 5, Creative 6, Professional 2, Technical 2), which enriches the enum parameter with expected result sizes. It does not discuss includeDetails, but the schema already covers it well.

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?

The description uses a specific verb ('List') and a specific resource ('15 built-in MDMagic templates'), then distinguishes itself from sibling list_all_templates by excluding custom uploads. This gives a clear, unambiguous purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly names an alternative ('Same as list_all_templates') and explains the difference ('but excludes the user's custom uploads'), then gives a direct usage directive: 'Use this when the user asks specifically about MDMagic's bundled templates rather than their personal ones.'

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

All mdmagic-mcp-server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: credit balance vs cost estimation, template listing scoped to all/built-in/custom, and conversion vs validation. The three list tools are explicitly named by scope, eliminating ambiguity.

Naming Consistency5/5

All tool names follow the same verb_noun snake_case pattern (check_, convert_, estimate_, get_, list_, recommend_, show_, validate_), making the API predictable and easy to navigate.

Tool Count5/5

10 tools is well within the ideal 3-15 range for a document conversion service. Each tool addresses a necessary step in the workflow (template selection, validation, cost estimation, conversion, credit monitoring) without redundancy.

Completeness4/5

The core lifecycle (pre-flight validation, cost estimation, conversion, balance checking, template discovery) is fully covered. Minor gaps exist—no template upload or settings update—but these are likely handled outside the MCP server, so the surface is complete for its intended agent workflows.

Resources