Zovo Graph Paper

Generate note paper

generate_note_paper

Read-onlyIdempotent

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.

Input Schema

Name	Required	Description
`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.

Output Schema

Name	Required	Description	Default
`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

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A3.9/5.0

Behavior4/5

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.

Conciseness4/5

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.

Completeness4/5

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.

Parameters3/5

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.

Purpose4/5

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.

Usage Guidelines4/5

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.

All Zovo Graph Paper tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?