Printable graph paper PDFs
Scored across 2 tools
The two tools split cleanly along paper category: grid-based graph paper versus lined/structured note paper. Descriptions explicitly state what each covers and both include negative scoping (e.g., no data plotting, no tracing worksheets), leaving no realistic overlap.
Both names follow the exact same generate_<object>_paper pattern with consistent snake_case and parallel structure. There is no ambiguity about which verb or resource convention is in use.
Two tools is slightly thin by the usual 3-15 guideline, but the server's purpose is narrow and each tool encapsulates a large parameterized family of outputs. Nothing suggests missing sibling tools that would need separate endpoints.
The surface covers the main printable-paper workflows: square/dot/isometric/hex/polar/log/engineering graph paper and lined/Cornell/music/tab/calligraphy note paper. Minor gaps like blank paper or combined templates are explicitly out of scope, so agents have clear boundaries rather than dead ends.
Use this when the user wants printable graph paper or grid paper as a PDF: square grid (1/4 inch, 5 mm, 1 mm, 4x4 or 5x5 per inch), dot grid, isometric or isometric dot, hexagon, polar, semi-log or log-log with chosen cycles, engineering paper, or a coordinate plane with numbered x and y axes. Lines are placed at true physical spacing and the grid is centred, with a calibration ruler. Up to 100 pages, Letter, Legal, Tabloid, A5, A4 or A3. Does not plot data, draw graphs of functions, or make tracing worksheets.
| Name | Required | Description | Default |
|---|---|---|---|
| axes | No | Square or dot grid only: draw numbered x and y axes through the centre (a coordinate plane), e.g. true. Default false. | |
| pages | No | Number of identical pages in the PDF, 1 to 100, e.g. 5 or "ten". Default 1. | |
| title | No | Optional heading printed at the top, e.g. "Physics lab 3". Longer titles are shortened to 80 characters. Latin, Greek and Cyrillic letters print. | |
| cycles | No | Semi-log and log-log: number of log cycles (decades) on the vertical axis, 1 to 6, e.g. 3. Default 3. | |
| margin | No | Page margin, e.g. "10 mm" or "0.5 in". Default 1/2 in on US pages, 10 mm on A pages; at least 0.2 in. | |
| spacing | No | Grid or line spacing with a unit, e.g. "5 mm", "1/4 inch", "0.5 cm", "5 squares per inch" or "4x4". For hex: across the flats; isometric: triangle side; polar: ring spacing; music: gap between staff lines; lined/cornell: line spacing; calligraphy: x-height. Default depends on the type (1/4 in on US pages, 5 mm on A pages). | |
| x_cycles | No | Log-log only: log cycles on the horizontal axis, 1 to 6, e.g. 2. Default 2. | |
| name_date | No | Print Name and Date lines at the top, e.g. true. Default false (Cornell notes: true). | |
| page_size | No | Paper size: Letter, Half Letter (5.5x8.5), Legal, Tabloid (11x17), A5, A4, A3 or B5, e.g. "A4". Default Letter (A4 for millimetre paper). "8.5x11", "US letter" and "A4 landscape" also work. | |
| angle_step | No | Polar only: degrees between spokes, e.g. 15 (default), 10, 5 or 30. | |
| line_color | No | Line colour as a name or hex, e.g. "light blue", "gray", "green", "black" or "#4A7FC1". Default depends on the type. | |
| paper_type | Yes | Paper type, e.g. "square" (graph paper), "dot", "isometric", "isometric dot", "hex", "polar", "semi-log", "log-log", "engineering", "quad ruled" (4 squares per inch), "millimetre paper" (1 mm grid), or "coordinate plane" for a grid with x and y axes. Lined, Cornell, music staff, guitar tab and calligraphy also work here. | |
| line_weight | No | Line thickness in points or a word, e.g. 0.4, "0.25 pt", "thin" or "bold". Default 0.4 pt (dots 1.4 pt). | |
| major_every | No | Draw a heavier line every N squares, e.g. 5 or 10. Default none (engineering: 5 per inch; 1 mm paper: 10). | |
| orientation | No | portrait or landscape, e.g. "landscape". Default portrait. | |
| hex_orientation | No | Hex only: "flat" (flat-top, default) or "pointy" (pointy-top). | |
| calibration_ruler | No | Print the 5 cm or 2 in check ruler in the bottom margin, e.g. true. Default true. |
| Name | Required | Description |
|---|---|---|
| label | Yes | |
| notes | Yes | |
| pages | Yes | |
| layout | Yes | |
| margin | Yes | |
| assumed | Yes | |
| request | Yes | |
| spacing | Yes | |
| downloads | Yes | |
| page_size | Yes | |
| paper_type | Yes | |
| spacing_mm | Yes | |
| spacing_pt | Yes | |
| orientation | Yes | |
| print_check | Yes | |
| page_width_mm | Yes | |
| page_height_mm | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish read-only, idempotent, non-destructive behavior, so the description's extra context is valuable: true physical line spacing, centred grids, a calibration ruler, a 100-page limit, and supported page sizes. It does not describe the PDF return structure in detail, but the output 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is front-loaded with the primary use case and then packs supported types, output traits, limits, and exclusions into a dense but purposeful paragraph. The long enumeration overlaps somewhat with the schema, but every clause contributes to matching or scoping.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a complex 17-parameter PDF generation tool with rich annotations and an output schema, the description covers the essential context: output format, supported paper types, physical spacing behavior, page limits, and exclusions. Nothing critical for correct invocation is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so all 17 parameters are already documented in detail. The description restates many supported paper types and spacing examples, but adds no syntax or meaning beyond what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb-and-resource: generating printable graph paper or grid paper as a PDF. It enumerates supported paper types and explicitly excludes plotting data or drawing function graphs, so an agent can distinguish this from the sibling note-paper tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives clear when-to-use guidance ('when the user wants printable graph paper or grid paper as a PDF') and explicit exclusions ('Does not plot data, draw graphs of functions, or make tracing worksheets'). The only missing piece is a direct reference to the sibling generate_note_paper as the alternative for note-paper requests.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Use this when the user wants a printable lined paper, Cornell notes template, music staff paper, guitar tab paper or calligraphy guide sheet as a PDF. Lined paper is wide, college or narrow ruled or any spacing; Cornell notes have a cue column, notes area, summary box and name/date/topic header; music staff paper sets staves per page; calligraphy guides set x-height, ascender:x-height:descender ratio and slant angle. Does not make letter tracing or handwriting practice worksheets.
| Name | Required | Description | Default |
|---|---|---|---|
| pages | No | Number of identical pages in the PDF, 1 to 100, e.g. 5 or "ten". Default 1. | |
| ratio | No | Calligraphy: ascender:x-height:descender ratio, e.g. "3:2:3" (default) or "1:1:1". | |
| title | No | Optional heading printed at the top, e.g. "Physics lab 3". Longer titles are shortened to 80 characters. Latin, Greek and Cyrillic letters print. | |
| margin | No | Page margin, e.g. "10 mm" or "0.5 in". Default 1/2 in on US pages, 10 mm on A pages; at least 0.2 in. | |
| ruling | No | Lined and Cornell paper: "wide" (11/32 in), "college" (9/32 in) or "narrow" (1/4 in), or a length such as "8 mm". Default college on US pages, 8 mm on A pages. | |
| staves | No | Music staff or guitar tab: staves per page, 1 to 20, e.g. 12. Default fills the page (12 music, up to 10 tab on Letter). | |
| spacing | No | Line spacing with a unit. Lined and Cornell: distance between lines, e.g. "8 mm" or "9/32 inch" (or use ruling). Music staff and guitar tab: gap between staff lines, e.g. "2 mm". Calligraphy: x-height, e.g. "5 mm". Default: college ruled on US pages, 8 mm on A pages, 2 mm staff gap, 5 mm x-height. | |
| name_date | No | Print Name and Date lines at the top, e.g. true. Default false (Cornell notes: true). | |
| page_size | No | Paper size: Letter, Half Letter (5.5x8.5), Legal, Tabloid (11x17), A5, A4, A3 or B5, e.g. "A4". Default Letter (A4 for millimetre paper). "8.5x11", "US letter" and "A4 landscape" also work. | |
| line_color | No | Line colour as a name or hex, e.g. "light blue", "gray", "green", "black" or "#4A7FC1". Default depends on the type. | |
| paper_type | No | Paper type, e.g. "lined" (default), "college ruled", "wide ruled", "cornell", "music staff", "guitar tab" or "calligraphy". | |
| line_weight | No | Line thickness in points or a word, e.g. 0.4, "0.25 pt", "thin" or "bold". Default 0.4 pt (dots 1.4 pt). | |
| major_every | No | Draw a heavier line every N squares, e.g. 5 or 10. Default none (engineering: 5 per inch; 1 mm paper: 10). | |
| orientation | No | portrait or landscape, e.g. "landscape". Default portrait. | |
| slant_angle | No | Calligraphy: slant line angle in degrees from horizontal, 30 to 90, e.g. 55 (default, copperplate). | |
| calibration_ruler | No | Print the 5 cm or 2 in check ruler in the bottom margin, e.g. true. Default true. |
| Name | Required | Description |
|---|---|---|
| label | Yes | |
| notes | Yes | |
| pages | Yes | |
| layout | Yes | |
| margin | Yes | |
| assumed | Yes | |
| request | Yes | |
| spacing | Yes | |
| downloads | Yes | |
| page_size | Yes | |
| paper_type | Yes | |
| spacing_mm | Yes | |
| spacing_pt | Yes | |
| orientation | Yes | |
| print_check | Yes | |
| page_width_mm | Yes | |
| page_height_mm | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the meaningful behavioral fact that output is a PDF and which structural features each paper type produces, though it says nothing about file location, naming or size limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with the activation trigger, then a dense second sentence grouping the knobs by paper type. Every clause maps to real tool behaviour; the semicolon-chained second sentence is heavy but not padded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With 16 optional parameters, an output schema and full annotations, the description is complete enough for an agent to pick a paper type and call it. Coverage of page_size, orientation and margin is left entirely to the schema, which is acceptable at this coverage level.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% with all 16 parameters documented, so the baseline is 3. The description's parameter talk (ruling styles, staves per page, ratio, slant angle, header) largely restates what the schema already states without adding format or constraint detail.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific family of outputs (lined paper, Cornell notes, music staff, guitar tab, calligraphy guide) delivered as a PDF, so an agent knows exactly what the tool produces. It never mentions the sibling generate_graph_paper, so the closest distinction is left implicit.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
"Use this when the user wants..." gives an explicit activation condition tied to user intent, and the closing sentence adds a genuine exclusion (no letter tracing or handwriting worksheets). The missing piece is routing: an agent choosing between this and generate_graph_paper gets no guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
generate_graph_papergenerate_note_paperTracing sheets & lined paper
Find free math worksheets (Pre-Algebra–Calculus, Statistics) as printable PDFs with answer keys.
Make printable nonogram puzzles for teachers, students and puzzle fans as a PDF with an answer key.
Create printable cryogenic lab, sample, tube and QR label sheets. Six templates; free, no login.
Add one secure layer between your agents and this server.