Skip to main content
Glama

validate_techpack

Read-onlyIdempotent

Use this tool to check whether a garment tech pack (JSON) is ready to send to a factory: missing fields, measurement chart checks (tolerances, how to measure, grading that grows with size, usual points for its family), fibre composition summing to 100 % with EU 1007/2011 fibre names, care label, and the Digital Product Passport fields it already covers. Returns a score and a list of fixes. From Cycle Studio; free and deterministic, no account needed.

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": {
      "techpack": "<techpack>"
    },
    "name": "validate_techpack"
  }
}

Input Schema

NameRequiredDescriptionDefault
familyNoOptional garment family to check its usual points of measure.
techpackYesThe tech pack with any keys: style_name, style_number, season, family/category, factory, composition, care, country_of_origin, fabric, weight, colourways, construction, trims, flats, measurements {sample_size, points: [{name, values: {size: cm}, tolerance, how_to_measure}]}.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint=false, so the safety profile is covered; the description adds genuinely new behavioral context — free, deterministic, no account needed — plus what is produced ('a score and a list of fixes') and the scope of what is inspected. It does not say how the score is scaled or what happens when the input is malformed, which keeps it below a 5.

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?

Front-loaded with the purpose, then a single dense enumeration of checks and a short outcome sentence. The middle clause is a long run-on list, but every element carries information and nothing is repeated.

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?

An output schema exists, so return-shape explanation is not required, and the description still summarizes the outputs. For a nested-object, free-form-input validator it covers scope, outcomes, and operating conditions well; only error/failure behavior 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 description coverage is 100% and the techpack object schema already lists all accepted keys, so the description adds little beyond it. The `family` parameter is only indirectly hinted at through 'usual points for its family' and is never explained as an input.

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 ('check whether a garment tech pack (JSON) is ready to send to a factory') and enumerates the exact check families it performs, which distinguishes it from the validate_dpp_* siblings that operate on DPP documents rather than full tech packs.

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?

Gives a clear triggering condition ('ready to send to a factory') and implies pre-submission validation, but never names an alternative tool or states exclusions (e.g. that DPP-document validation lives in validate_dpp_document).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources