Mathter MCP Server

Overview Schema Source Related Servers Discussions Admin

Generate a Mathter worksheet pack

generate_worksheet_pack

Create a printable math worksheet pack as a local PDF and return its file path, using a selected skill and grade; call list_skills first to pick valid options.

Instructions

Generate a printable math worksheet pack as a PDF and save it to this computer, then return the file path. The pack is billed to the Mathter account that owns MATHTER_API_KEY, under that account's normal monthly allowance — the same as making it on mathter.ca. Call list_skills first to choose a valid skill for the grade. Logo and branding come from the account itself and cannot be set here.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`seed`	No	Fixes the random number generator, so the same seed reproduces the same pack. Default random.
`chart`	No	Multiplication only: print a times-table chart instead of worksheets. "filled" is a reference chart, "blank" is one to fill in.
`focus`	No	Single-number drill, e.g. 7 for the seven times table. Only applies to the four fact skills: addition, subtraction, multiplication, division.
`grade`	Yes	Grade level, 0 (kindergarten) to 12. Must be a grade the chosen skill teaches — list_skills returns the grades for each skill.
`skill`	Yes	Which math skill the pack drills, e.g. "multiplication". Call list_skills first and use one of the keys it returns: the set changes, and the skill must be one the chosen grade is taught. An unknown or out-of-grade skill is rejected with 400.
`style`	No	Typography/layout preset, default "modern". Plan-gated and rejected outright if the account cannot use it: free accounts have "modern" only, Standard adds "classic" and "notebook", Premium has all six. Omit it unless the person asked for a look.
`theme`	No	Colour palette for the pack. Available on every plan. Defaults to teal.	teal
`timed`	No	Mad-minute timed drill. Only applies to addition, subtraction, multiplication and division.
`title`	No	Title printed on the pack, default "Math Lesson". Truncated at 80 characters.
`diagrams`	No	Geometry skills only: labelled figures instead of text prompts. Ignored for other skills.
`shopName`	No	Branding name printed on the pack. Premium only — on any other account it is silently replaced with "Mathter.ca" and the pack still generates. Members of a school organisation always get the organisation's own branding instead.
`difficulty`	No	Difficulty band, default "medium".
`focusOrder`	No	Order of a focus drill, default sequential. Only applies when focus is set.
`graphBlank`	No	Coordinate grids are blank (unlabelled) by default so students set their own scale. Pass false for a labelled ±10 grid. Only meaningful where the skill prints a graph.
`unitSystem`	No	Units for measurement questions, default metric. Mainly affects unit-conversion skills.
`includeCover`	No	Print a cover page. Default true, but silently off for free accounts (Standard and up).
`includeLesson`	No	Print the "how to" lesson page. Default true, silently off for free accounts (Standard and up).
`worksheetCount`	No	How many worksheets in the pack. Clamped to the account's plan — free 2, Standard 10, Premium 25 — so asking for more is harmless but gets fewer. Omitted, it is 10 or the plan's cap, whichever is smaller: a free account's default pack is 2 sheets.
`problemsPerPage`	No	Questions per page, default 12. Clamped down to whatever actually fits one page for this skill, grade and layout, so a large number simply gives the densest legal page.
`workedSolutions`	No	Step-by-step worked solutions in the answer key. Only has an effect for skills that have steps authored; silently ignored elsewhere.
`includeAnswerKeys`	No	Print answer keys. Default true on every plan; send false to omit them.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true. The description adds billing behavior (charged to the account's monthly allowance), the physical side effect (saving a PDF to the computer), and a branding limitation. It does not mention error responses for invalid skills, but the schema covers that.

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?

Four sentences front-load the purpose, then cover billing, prerequisite, and branding. Each sentence earns its place, though the branding constraint partially duplicates the schema; the description remains compact and readable.

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?

For a complex 21-parameter tool with no output schema, the description covers purpose, billing, a required prerequisite, and a key limitation. Remaining details—plan gates, defaults, error behavior—are thoroughly documented in the schema, so the description is complete enough for correct invocation.

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?

With 21 parameters at 100% schema description coverage, the schema already documents every field thoroughly. The description adds no parameter-level detail beyond repeating the list_skills prerequisite and the branding constraint, both of which are already in the schema. Baseline 3 is appropriate.

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 opens with a specific verb ('Generate') and resource ('printable math worksheet pack as a PDF'), states the side effect (save to this computer) and the return value (file path). It also names the sibling tool list_skills as the required first step, so an agent can distinguish the two without opening either 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?

It gives an explicit prerequisite: 'Call list_skills first to choose a valid skill for the grade.' It also states a hard constraint (branding cannot be set here), but does not describe when to choose this tool over a hypothetical alternative, since none exists; the guidance is context-setting rather than routing.

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

Deploy Server

Generate a Mathter worksheet pack

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools