Levels Custom Apparel

Build an order

build_order

Read-only

Build the customer's order: one garment, how many of each size in each colour, how the logo is made and where it goes. Checks stock, prices it and gives a link that opens the garment with all of that chosen. The customer adds their logo there, checks it and pays; nothing is ordered until they do.

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": {
      "slug": "<slug>",
      "lines": "<lines>"
    },
    "name": "build_order"
  }
}

Input Schema

Name	Required	Description
`slug`	Yes	The product's slug, from search_products
`lines`	Yes	One entry per colour.
`method`	No	How the logo is applied. Default PRINT.
`position`	No	Where the logo goes. Default front, the left chest.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.8/5.0

Behavior5/5

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

While annotations indicate safety, the description adds crucial behavioral steps: it 'Checks stock' and 'prices' the item, and critically, specifies the output is a link, confirming the process is consultative, not transactional.

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?

It is a single, dense paragraph, which could be improved with bullet points for optimal scanning. However, it is efficient and all sentences serve the purpose of explaining the end-to-end function.

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?

Given the full parameter coverage and clear safety hints, the description is complete because it defines the tool's *process* and its *outcome* (a configured link), which is the most important behavioral information absent from the structured fields.

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?

With 100% schema coverage, the baseline is 3. The description adds value by grouping parameters into clear functional categories: 'how many of each size in each colour,' 'how the logo is made and where it goes,' giving semantic context to the input collection.

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?

The tool clearly defines its role: to assemble and quote a customer's custom garment order. It distinguishes this setup/quoting function from other potential ordering actions like `start_order` or `get_product`.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit boundaries for when to use the tool by stating its output (a link to configure and pay) and its limitation: 'nothing is ordered until they do.' This provides excellent context on the workflow and handoff to the user.

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

All Levels Custom Apparel 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.

Resources

Need Help?