Skip to main content
Glama

get_techpack_template

Read-onlyIdempotent

Use this tool when someone needs to prepare a tech pack (technical sheet / ficha técnica) for a factory: give the garment family (sweatshirt, knitwear, denim, bags, tshirt, dress) and get the sections a factory needs, the points of measure with how to measure each one and usual tolerances, materials/BOM and trims, construction, EU labelling rules, quality checks, typical lead time, and which fields also feed the EU Digital Product Passport. 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": {
      "family": "<family>"
    },
    "name": "get_techpack_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizesNoSize run, default XS–XL.
familyYesGarment family or a garment name: sweatshirt, hoodie, knitwear, sweater, denim, jeans, bag, tote, t-shirt, dress, blouse…
sample_sizeNoSize the sample is made in, default M.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, closed-world, and idempotent behavior; the description adds genuinely new operational context by declaring the tool free, deterministic, and requiring no account — useful for an agent deciding whether a call is safe and repeatable. It stops short of describing size of output or failure modes for an unsupported family.

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 front-loaded sentence with the trigger first and a dense payload list after it; every clause carries information. It is a long run-on with a comma-spliced enumeration and the provenance/free note tacked on at the end, which costs it a point on structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 values need not be spelled out, yet the description still tells the agent the shape of the answer well enough to set expectations. Combined with the free/deterministic note and full schema coverage, nothing material is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, but the description goes further by explaining what the family parameter actually drives (which section set, measurement guidance, tolerances, and DPP fields come back) and mentions the default size run behavior implicitly through the sizes/sample_size defaults. That is real meaning beyond the schema text.

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 ('prepare a tech pack') and enumerates exactly what the caller receives: sections, points of measure with tolerances, BOM/trims, construction, EU labelling, QC, lead time, and DPP-feeding fields. This clearly separates it from validate_techpack, which shares the domain but not the generate-a-template action.

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?

Opens with an explicit trigger ('Use this tool when someone needs to prepare a tech pack for a factory') and states the input needed (the garment family). It does not name a when-not condition or point at validate_techpack as the follow-up/alternative, so it falls short of a 5.

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