Skip to main content
Glama
Sign In

Punchneedle.ai

by ai.punchneedle
OverviewDiscussionsAdmin

Make a pattern from an image

make_pattern_from_image
Read-onlyIdempotent

Converts a public PNG, JPEG or WebP image into a punch needle pattern with the website's pattern converter. Returns the pattern as a stitch grid preview, its colours and the yarn each colour needs in a fine-wool kit and a rug-wool kit.

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": "make_pattern_from_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoSame value as image_url.
sizeNoSame value as width.
unitNoUnit of the width; the default is cm.
imageNoSame value as image_url.
widthNoFinished width of the pattern in the chosen unit: 20 to 2000 mm, 2 to 200 cm or 0.8 to 78.7 in. The default is 20 cm.
colorsNoSame value as colours.
coloursNoLargest number of yarn colours in the pattern, from 2 to 32. The default is 6.
imageUrlNoSame value as image_url.
image_urlNoPublic web address (https) of a PNG, JPEG or WebP image of at most 4 MB.

Output Schema

NameRequiredDescriptionDefault
itemYes
viewYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds what is actually produced (stitch grid preview, colours, and yarn requirements in both a fine-wool and rug-wool kit), which is genuinely useful context beyond the annotations; it does not cover failure behaviour for unreachable or oversized images.

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 sentences, front-loaded with the conversion action and followed by the concrete outputs. No filler or restatement of the title.

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 an output schema present, the description need not spell out return structure, and the annotations cover safety, so the essentials are present. The one gap is that the schema declares zero required parameters despite the tool being useless without an image address, and the description does not clarify that an image URL is in practice mandatory or which alias to use.

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 coverage is 100% and each parameter, including the allowed image formats, 4 MB cap, width ranges and colour range, is already documented in the schema. The description contributes no additional meaning about the alias pairs (url/image/imageUrl/image_url) or which value is effectively needed.

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 — 'Converts a public PNG, JPEG or WebP image into a punch needle pattern' — and names the producing mechanism ('the website's pattern converter'). The 'from an image' framing distinguishes it from siblings that operate on an existing pattern (get_pattern, resize_pattern).

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?

Usage is only implied: an agent can infer it should be used when it holds an image URL and wants a new pattern. There is no explicit statement of when to prefer it over resize_pattern, find_patterns, or match_materials, and no exclusions or prerequisites.

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