Skip to main content
Glama
Sign In

Punchneedle.ai

by ai.punchneedle
OverviewDiscussionsAdmin

Resize a pattern

resize_pattern
Read-onlyIdempotent

Rescales a library pattern, or a design of a given size, to a new width or height with the proportions kept. Returns the new dimensions, the number of printed A4 and US Letter sheets and, for a library pattern, the yarn at the new size.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "resize_pattern"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoSame value as pattern.
unitNoUnit of the sizes; the default is cm.
widthNoCurrent width of a design that is not a library pattern, in the chosen unit.
heightNoCurrent height of a design that is not a library pattern, in the chosen unit.
patternNoLibrary pattern id such as cat or sunflower, or its name.
new_widthNoNew width in the chosen unit, from 10 mm to 2000 mm. The height follows the proportions.
new_heightNoNew height in the chosen unit, up to 2000 mm. The width follows the proportions.

Output Schema

NameRequiredDescriptionDefault
itemYes
viewYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so safety is covered; the description adds genuinely new behavior — that proportions are always preserved and which companion values (dimensions, sheet counts, yarn) come back. It stops short of noting that a yarn result only applies in the library-pattern case beyond the one clause already given, which is a minor gap.

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?

Two tight sentences: the action and its two modes come first, the returned values second. No filler, no restatement of the title, and the proportional-scaling constraint is embedded where it matters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values needn't be spelled out, and the description is adequate for a seven-parameter tool whose schema is fully documented. What it omits is the combination rule for zero required parameters — that pattern/id and width/height are alternative input modes and that new_width or new_height is needed — which an agent must infer from the schema alone.

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 the baseline is 3 and every parameter is already documented, including the note that the other dimension follows the proportions. The description's 'library pattern vs design of a given size' framing helps map intent to parameter groups but adds no syntax, ranges, or exclusivity rules beyond the schema.

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?

States a specific verb and resource ('Rescales a library pattern, or a design of a given size') and names the two operating modes, so an agent knows exactly what the tool does. It does not explicitly contrast with siblings like get_pattern or find_patterns, but the function is unambiguous on its own.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implicitly tells the agent that a library pattern is resized via one path and a custom design via another, which is useful context. However, it never states when to prefer this tool over siblings such as get_pattern, nor does it state the precondition that at least one of pattern/id or width+height must be supplied.

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

All Punchneedle.ai toolsInspect
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