Skip to main content
Glama

Read Template Maker

tmaker_read
Read-onlyIdempotent

Reads Template Maker data: skeleton guide and placeholder rules, standard designs, saved projects. Validates skeleton HTML without saving it.

Input Schema

NameRequiredDescriptionDefault
idNoSynonym for design_id or project_id.
tmplNoSkeleton HTML.
actionYesOperation to run. Each oneOf entry describes one action and lists its parameters.
offsetNoRecords to skip from the start of a list; overrides page. A list reply cut at its size limit names the offset that follows in next.
design_idNoStandard design id from designs_list (usually 101 or more).
project_idNoSaved project id from project_list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / action / oneOf
      Previous value: -[
      -  {
      -    "const": "skeleton_guide",
      -    "description": "Returns the skeleton guide (markdown)."
      -  },
      -  {
      -    "const": "skeleton_rules",
      -    "description": "Returns the placeholder codes allowed in skeleton HTML. Optional: offset."
      -  },
      -  {
      -    "const": "designs_list",
      -    "description": "Lists standard designs. Optional: offset."
      -  },
      -  {
      -    "const": "design_get",
      -    "description": "Returns one standard design (id in design_id or id). Optional: design_id, id."
      -  },
      -  {
      -    "const": "project_list",
      -    "description": "Lists saved projects. Optional: offset."
      -  },
      -  {
      -    "const": "project_get",
      -    "description": "Returns one saved project (id in project_id or id). Optional: project_id, id."
      -  },
      -  {
      -    "const": "skeleton_validate",
      -    "description": "Checks skeleton HTML without saving it. Required: tmpl."
      -  }
      -]New value: +[
      +  {
      +    "const": "skeleton_guide",
      +    "description": "Returns the skeleton guide (markdown)."
      +  },
      +  {
      +    "const": "skeleton_rules",
      +    "description": "Returns the placeholder codes allowed in skeleton HTML. Optional: offset."
      +  },
      +  {
      +    "const": "designs_list",
      +    "description": "Lists standard designs. Optional: offset."
      +  },
      +  {
      +    "const": "design_get",
      +    "description": "Returns one standard design (id in design_id or id). Required: design_id or id."
      +  },
      +  {
      +    "const": "project_list",
      +    "description": "Lists saved projects. Optional: offset."
      +  },
      +  {
      +    "const": "project_get",
      +    "description": "Returns one saved project (id in project_id or id). Required: project_id or id."
      +  },
      +  {
      +    "const": "skeleton_validate",
      +    "description": "Checks skeleton HTML without saving it. Required: tmpl."
      +  }
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / action / oneOf
      Previous value: -[
      -  {
      -    "const": "skeleton_guide",
      -    "description": "Returns the skeleton guide (markdown)."
      -  },
      -  {
      -    "const": "skeleton_rules",
      -    "description": "Returns the placeholder codes allowed in skeleton HTML."
      -  },
      -  {
      -    "const": "designs_list",
      -    "description": "Lists standard designs."
      -  },
      -  {
      -    "const": "design_get",
      -    "description": "Returns one standard design (id in design_id or id). Optional: design_id, id."
      -  },
      -  {
      -    "const": "project_list",
      -    "description": "Lists saved projects."
      -  },
      -  {
      -    "const": "project_get",
      -    "description": "Returns one saved project (id in project_id or id). Optional: project_id, id."
      -  },
      -  {
      -    "const": "skeleton_validate",
      -    "description": "Checks skeleton HTML without saving it. Required: tmpl."
      -  }
      -]New value: +[
      +  {
      +    "const": "skeleton_guide",
      +    "description": "Returns the skeleton guide (markdown)."
      +  },
      +  {
      +    "const": "skeleton_rules",
      +    "description": "Returns the placeholder codes allowed in skeleton HTML. Optional: offset."
      +  },
      +  {
      +    "const": "designs_list",
      +    "description": "Lists standard designs. Optional: offset."
      +  },
      +  {
      +    "const": "design_get",
      +    "description": "Returns one standard design (id in design_id or id). Optional: design_id, id."
      +  },
      +  {
      +    "const": "project_list",
      +    "description": "Lists saved projects. Optional: offset."
      +  },
      +  {
      +    "const": "project_get",
      +    "description": "Returns one saved project (id in project_id or id). Optional: project_id, id."
      +  },
      +  {
      +    "const": "skeleton_validate",
      +    "description": "Checks skeleton HTML without saving it. Required: tmpl."
      +  }
      +]
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Records to skip from the start of a list; overrides page. A list reply cut at its size limit names the offset that follows in next.",
      +  "type": "number"
      +}
  3. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered elsewhere. The only extra behavioral note is that skeleton validation does not persist anything ('without saving it'), but that same fact is already stated in the schema's skeleton_validate entry, so the description adds little beyond structured fields.

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?

Two short, front-loaded sentences with no filler; the resource enumeration comes first and the validation caveat second. It is efficient, though it could have traded one clause for an explicit routing hint to the write/delete siblings.

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?

With 100% schema coverage, an output-schema-free design, and annotations covering read-only/idempotency, the description is nearly complete for a multi-action read tool. The remaining gap is routing guidance to sibling mutation tools and pagination behavior, both of which are only partly addressed elsewhere.

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 description coverage is 100% and the action enum documents each operation along with its required id/tmpl/offset parameters. The description names the data categories but supplies no syntax, defaults, or id-source detail beyond what the schema already gives, so the baseline 3 applies.

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?

The description names a specific verb (reads) plus the concrete resource groups it exposes: skeleton guide, placeholder rules, standard designs, saved projects, and skeleton validation. An agent can distinguish it from tmaker_write/tmaker_delete/tmaker_publish by the read/validate framing, though it never explicitly names those siblings.

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 only implied by the word 'Reads' and by the per-action oneOf descriptions in the schema; the description itself offers no when-to-use, when-not-to-use, or explicit alternative (e.g. use tmaker_write to modify a project).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.