Skip to main content
Glama

Zovo Graph Paper

Generate graph paper

generate_graph_paper
Read-onlyIdempotent

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.

Input Schema

NameRequiredDescriptionDefault
axesNoSquare or dot grid only: draw numbered x and y axes through the centre (a coordinate plane), e.g. true. Default false.
pagesNoNumber of identical pages in the PDF, 1 to 100, e.g. 5 or "ten". Default 1.
titleNoOptional heading printed at the top, e.g. "Physics lab 3". Longer titles are shortened to 80 characters. Latin, Greek and Cyrillic letters print.
cyclesNoSemi-log and log-log: number of log cycles (decades) on the vertical axis, 1 to 6, e.g. 3. Default 3.
marginNoPage 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.
spacingNoGrid 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_cyclesNoLog-log only: log cycles on the horizontal axis, 1 to 6, e.g. 2. Default 2.
name_dateNoPrint Name and Date lines at the top, e.g. true. Default false (Cornell notes: true).
page_sizeNoPaper 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_stepNoPolar only: degrees between spokes, e.g. 15 (default), 10, 5 or 30.
line_colorNoLine colour as a name or hex, e.g. "light blue", "gray", "green", "black" or "#4A7FC1". Default depends on the type.
paper_typeYesPaper 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_weightNoLine 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_everyNoDraw a heavier line every N squares, e.g. 5 or 10. Default none (engineering: 5 per inch; 1 mm paper: 10).
orientationNoportrait or landscape, e.g. "landscape". Default portrait.
hex_orientationNoHex only: "flat" (flat-top, default) or "pointy" (pointy-top).
calibration_rulerNoPrint the 5 cm or 2 in check ruler in the bottom margin, e.g. true. Default true.

Output Schema

NameRequiredDescriptionDefault
labelYes
notesYes
pagesYes
layoutYes
marginYes
assumedYes
requestYes
spacingYes
downloadsYes
page_sizeYes
paper_typeYes
spacing_mmYes
spacing_ptYes
orientationYes
print_checkYes
page_width_mmYes
page_height_mmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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.

Conciseness4/5

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.

Completeness5/5

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.

Parameters3/5

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.

Purpose5/5

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.

Usage Guidelines4/5

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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources