Skip to main content
Glama
seinun-ai

Maestro Career Studio

Official
by seinun-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Create Template Draft

create_template_draft

Create a draft resume template in LaTeX or Typst within Maestro Career Studio, then optionally validate it by test-compiling.

Instructions

Create a DRAFT template. engine defaults to 'latex'. Pass engine='typst' for Typst — then source is REQUIRED: raw .typ text (no Jinja, no escape filters; read via json(bytes(sys.inputs.resume)) / json(bytes(sys.inputs.fmt)); engine is immutable after creation).

Both engines consume the same resume JSON (contact, summary,
skills[].{category,items}, experience/projects/education, certifications,
extra_sections). Typst reads r.contact.name etc.; optional fields arrive
as `none` — guard with `!= none`. LaTeX uses resume.* with |latex_escape
on every value.

Typst constraints: dates arrive PRE-FORMATTED server-side (fmt.date_format
is not read). Package imports (`#import "@preview/..."` or any `@...`
import) are REJECTED (no external packages). Fonts: only
vendored XCharter plus typst's embedded defaults (e.g. Libertinus Serif);
any other family compiles WITHOUT error and silently substitutes. A template
that does not render r.extra_sections (both `entries` and `bullets` shapes)
hard-fails on resumes with custom sections; get_template('typst-classic')
shows the block.

LaTeX: omit `source` to start from the canonical starter. Given source
must be a complete compilable document (\documentclass + preamble) as
Jinja2 with blocks ((* *)), variables ((( ))), comments ((# #)). The source
is raw LaTeX: bare `&` for tabular cells, `\&` for a literal ampersand;
HTML entities such as `&` are not decoded. Includable:
((* include '_header.tex.j2' *)). Spacing and look can be wired to `fmt.*`
(full knob list on get_template) instead of hard-coded values;
get_template('default') is a starting point.

validate=True test-compiles in the same call (status/last_error). A LaTeX
draft cannot validate on a backend with no TeX (list_templates →
engine_available); engine='typst' works there. Not usable until validation
succeeds. `id` is a slug: [a-z0-9_-].

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
engineNolatex
sourceNo
validateNo
display_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare the safety profile (write, non-destructive, non-idempotent); the description goes far beyond: engine is immutable after creation, drafts are not usable until validation succeeds, LaTeX cannot validate on a backend without TeX, Typst rejects @-imports, unknown fonts silently substitute without error, templates that skip r.extra_sections hard-fail, and HTML entities are not decoded. These are exactly the non-obvious behaviors an agent must know before writing source.

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?

Front-loaded with the core action and the engine branch, then progressively details Typst constraints, LaTeX format, and validation. Dense but each sentence carries operative information. It is long for a tool description and the Typst/LaTeX blocks could be slightly tightened, so it is not a model of concision, but little is 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 5-parameter, no-output-schema mutation tool, the description covers the full call surface plus the failure modes: what source must contain per engine, what validation does and reports (status/last_error), engine availability via list_templates, and post-creation immutability. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does: engine default and the source-required-for-typst rule, the exact required format of source per engine (raw .typ with sys.inputs access vs. complete Jinja2 LaTeX document with ((* *)), ((( ))), ((# #)) blocks), validate's test-compile semantics, and id's slug charset [a-z0-9_-]. Only display_name is left undocumented, which is self-evident.

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 + resource + lifecycle state: 'Create a DRAFT template.' Distinguishes itself from siblings by naming the read path (get_template), the enumeration tool (list_templates), and the mutation follow-up (update_template_draft implied), so an agent can place it in the template lifecycle without opening another schema.

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 concrete conditional guidance: engine defaults to 'latex'; pass engine='typst' and then source becomes REQUIRED; omit source for the LaTeX canonical starter; validate=True test-compiles in the same call. It also names get_template('default') and get_template('typst-classic') as starting points. It does not explicitly route 'editing an existing draft' to update_template_draft, so it stops short of 5.

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

Deploy Server

Other Tools