Skip to main content
Glama

Kizupi

Math word problem worksheet

make_worksheet
Read-only

Makes a free printable sheet of 8 math word problems for a US grade (1 to 6), optionally on one topic (see list_worksheet_topics). Each problem comes with its answer, the worked line, and a focus question a grown-up can ask instead of giving the answer. Returns a printable link. Use the same seed to get the same sheet again.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "grade": "<grade>"
    },
    "name": "make_worksheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNoLeave out for a new sheet.
gradeYesSchool grade, 1 to 6 (US).
topicNoA topic slug for that grade, e.g. "fraction" or "multiplication-and-division". Leave out for a mix of the grade's skills.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint, openWorldHint=false), and the description adds real value beyond them: the output shape (each problem with answer, worked line, and a focus question for an adult) and the deterministic seed behavior. Nothing is disclosed about limits, caching, or the printable link's lifetime, which keeps it short of a 5.

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?

One tight paragraph with no filler: capability, scope, sibling reference, return contents, and reproducibility are each stated once. The core action is front-loaded in the first clause.

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 3-parameter generator with no output schema, the description supplies everything needed: required grade range, optional topic routing, optional seed reproducibility, and what the returned sheet and link contain.

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 coverage is 100%, so the 3 baseline is already met, and the description adds determinism semantics for seed ('same seed to get the same sheet') and cross-references topic slugs to a sibling tool. Only grade semantics are left entirely to the schema.

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 and resource (makes a printable sheet of 8 math word problems) plus scope constraints (US grades 1-6, optional single topic). It also distinguishes itself from siblings by routing topic discovery to list_worksheet_topics.

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 clear usage context: omit the topic for a mixed-skill sheet, consult list_worksheet_topics for valid topic slugs, and reuse a seed to reproduce a sheet. It does not spell out when-not-to-use or how it relates to list_skills, but the operating guidance is unambiguous.

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.

Resources