Skip to main content
Glama
CLO Atelier

CLO Atelier

by benproj

Get pattern geometry

clo_get_patterns
Read-only

Get outline geometry for pattern pieces, including point coordinates, line indices and lengths, fabric, grain, layer, and seam groups, to find matching lines and lengths before sewing.

Instructions

Outline geometry for one or more pattern pieces: points (mm), outline lines with index, length and whether curved, plus fabric, grain, layer, mesh particle distance, arrangement and seam groups. Use it to find line indices and matching lengths before sewing. Omit pattern_indices for every piece.

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

Input Schema

NameRequiredDescriptionDefault
pattern_indicesNoPieces to describe. Omit for all pieces.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.9/5.0
Behavior4/5

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

With only readOnlyHint supplied, the description picks up real slack by disclosing the exact shape and units of the returned data (mm measurements, per-line index/length/curved flag), which is the main behavioral unknown for a getter. It omits payload-size or batching caveats when all pieces are requested, so it stops short of the top score.

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?

The payload enumeration is front-loaded in one dense sentence, then usage, then the default behavior — a sensible order. The final sentence duplicates what the schema already says, which is the one piece of waste.

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 one-parameter read-only getter with no output schema, the description adequately covers both inputs and the returned structure, so an agent can call it and interpret results without opening anything else. Only edge behavior (very large results when all pieces are requested) is unaddressed.

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 the single parameter is already documented as 'Pieces to describe. Omit for all pieces.' The trailing sentence 'Omit pattern_indices for every piece' is essentially a restatement rather than added meaning, so the baseline of 3 applies.

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 verb and resource ('Outline geometry for one or more pattern pieces') and enumerates exactly what comes back: points in mm, outline lines with index/length/curvature, plus fabric, grain, layer, mesh particle distance, arrangement and seam groups. That is far more specific than a name restatement, though it never explicitly contrasts itself with lookalike readers such as clo_get_fabric or clo_list_arrangement_points.

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 it to find line indices and matching lengths before sewing' gives a concrete workflow trigger that points forward to clo_sew without naming it as an alternative. It tells the agent when the tool is right but offers no exclusions or explicit 'use X instead' routing.

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