Skip to main content
Glama
cshum

Imagor MCP

Official

parse_template

Convert an imagor path into an editable template, so you can adjust the JSON and re-render instead of retyping.

Instructions

Read an imagor path back into a template, so one you already have can be edited rather than retyped. This is the inverse of render_template and the two are meant to be used together: render, look, adjust the JSON, render again. Read get_imagor_skill before composing anything. Note that the geometry comes back absolute - a path records the numbers a template resolved to, not the forms it was written in. To check a path without converting it, use validate_imagor_path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesan imagor path, or a full URL, to read back into a template. The path is what render_template produces, so a path you already have can be turned into something you can edit.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
slotsYes
valuesNo
backgroundYes
canvas_widthYes
canvas_heightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.7.10
    • changedOutput schema / properties / slots / items / properties / filters / description
      Previous value: -"for image or rect: filters applied to this slot's own source, written without the filters: prefix, e.g. smart/filters:round_corner(230,230,fff)"New value: +"for image or rect: filters applied to this slot's own source, colon-separated, for example smart():round_corner(230,230,fff). The filters: prefix is added for you. Measured: a slash between filters 404s"
    • changedOutput schema / properties / slots / items / properties / slots / items / properties / filters / description
      Previous value: -"for image or rect: filters applied to this slot's own source, written without the filters: prefix, e.g. smart/filters:round_corner(230,230,fff)"New value: +"for image or rect: filters applied to this slot's own source, colon-separated, for example smart():round_corner(230,230,fff). The filters: prefix is added for you. Measured: a slash between filters 404s"
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the key behavioral trait that geometry is returned as absolute numbers rather than the written forms, which an agent would otherwise get wrong. It doesn't state output shape, but an output schema exists, so this is the one remaining gap.

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?

Front-loads the core purpose, then workflow, then prerequisite, then the subtle absolute-geometry caveat, then the alternative. Four sentences, each earning its place with 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?

Covers purpose, workflow pairing with render_template, prerequisite skill, the non-obvious absolute-geometry behavior, and the sibling alternative. With an output schema handling return values and full schema coverage on the parameter, nothing an agent needs is missing.

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%, so the single 'path' parameter is already documented in the schema. The description adds only that it accepts a full URL and is what render_template produces, which overlaps with the schema text, so baseline 3 applies.

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 back'/'parse') and resource (imagor path -> template), and explicitly distinguishes itself as the inverse of render_template. An agent can tell it apart from validate_imagor_path and render_template without opening any schema.

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?

Explicitly describes the render/look/adjust/render workflow with render_template, names get_imagor_skill as a prerequisite, and routes to validate_imagor_path for path-checking-without-conversion. When-to-use and alternatives are both covered.

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