Skip to main content
Glama
Sign In

Punchneedle.ai

by ai.punchneedle
OverviewDiscussionsAdmin

Match materials

match_materials
Read-onlyIdempotent

Checks whether a punch needle, a fabric and a yarn work together, using the website's material guidance. Returns the verdict for each part, what to change and the checks to make on a swatch.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "needle": "<needle>",
      "fabric": "<fabric>",
      "yarn": "<yarn>"
    },
    "name": "match_materials"
  }
}

Input Schema

NameRequiredDescriptionDefault
yarnYesYarn or fibre: rug yarn, bulky knitting yarn, worsted yarn, sport or sock yarn, or embroidery floss.
fabricYesFoundation fabric: rug-punching monk's cloth, rug linen, rug warp or punch-embroidery weaver's cloth.
needleYesNeedle family: Oxford regular point, Oxford fine yarn point, or a miniature embroidery punch needle for floss.

Output Schema

NameRequiredDescriptionDefault
itemYes
viewYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and side-effect profile is fully covered. The description adds that the result is a verdict per part, suggested changes, and swatch checks, which is modest extra context. Since an output schema exists, the return-value detail duplicates structured data rather than adding undisclosed behavior.

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?

A single sentence, front-loaded with the core check, followed by the output summary in the same sentence. No filler or repetition. Slightly dense but every clause contributes.

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?

For a read-only, three-required-parameter tool with 100% schema coverage and an output schema, the definition supplies the essential purpose and a sketch of the response. Nothing critical to correct invocation is missing, though a note on unsupported material combinations would have made it complete.

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's description lists the accepted material families with concrete examples. The description only restates the three inputs (needle, fabric, yarn) without adding meaning, formatting advice, or failure-mode guidance beyond the schema. Baseline 3 is appropriate when the schema carries this much 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 opens with a concrete verb and resource: "Checks whether a punch needle, a fabric and a yarn work together." That names all three inputs and the compatibility verdict, which clearly separates it from siblings like calculate_yarn or find_patterns. It does not explicitly name an alternative tool, which keeps it at 4 rather than 5.

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 this is the tool for checking material compatibility before starting a project. There is no statement of when not to use it, and no mention of get_material_guide or other siblings as fallbacks for adjacent needs.

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