Punchneedle.ai

Find patterns

find_patterns

Read-onlyIdempotent

Lists the original punch needle patterns in the Punchneedle.ai library, filtered by theme and level. Each pattern shows its finished size, number of colours, level and preview image.

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

Input Schema

Name	Required	Description
`level`	No	Level of the patterns: beginner for the website's beginner collection, or any for all patterns.
`query`	No	Same value as theme.
`theme`	No	Theme or collection such as flowers, animals, geometric, Christmas, Halloween, hearts, landscapes, rainbows, food or primitive, or a word from a pattern's name.
`category`	No	Same value as theme.
`collection`	No	Same value as theme.
`difficulty`	No	Same value as level.

Output Schema

Name	Required	Description	Default
`view`	Yes
`items`	Yes
`links`	No
`notes`	No
`title`	No
`total`	Yes
`request`	Yes
`pageSize`	Yes
`subtitle`	No
`nextCursor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile carries little weight. The description adds that each result includes finished size, colour count, level and a preview image, but says nothing about result counts, pagination or ordering, which are the behaviors an agent would still need to infer.

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?

Two sentences, filter scope front-loaded, no filler. The second sentence about returned fields overlaps with the output schema, so it is not strictly earning its place, but the description remains tight.

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?

Output schema and annotations are present, so return values and safety need no explanation. However, for a list tool with six optional, heavily aliased parameters, the description omits default behavior when no filter is supplied and whether results are paginated or bounded.

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%, so the baseline is 3. The description only restates the theme and level filters and does not clarify the notable alias structure in the schema (query/category/collection all identical to theme; difficulty identical to level) or whether the filters combine with AND semantics.

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: 'Lists the original punch needle patterns in the Punchneedle.ai library', plus the filter dimensions (theme and level). An agent can tell this is the browse/list operation versus the detail-fetching sibling get_pattern, though no sibling is named.

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 by 'filtered by theme and level'; there is no explicit statement of when to reach for this versus get_pattern, or what happens with no filters at all. An agent can infer the browse use case, but nothing is spelled out.

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

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