Skip to main content
Glama
Sign In

PatchDesign.AI

by ai.patchdesign
OverviewDiscussionsAdmin

Price a custom patch

quote_patch
Read-onlyIdempotent

Price a custom patch from the live PatchDesign.AI production price table: type, size and quantity in, the per-patch and total price in USD out, with the next quantity breaks and what the price already includes (artwork, a pre-production sample, worldwide shipping). The price returned is the customer's price, not a starting figure. No quote is needed unless they choose a backing or border with no set price; then that price is confirmed within 2 business hours. There is no minimum: quantity 1 returns the sample prices, and by default quote the price breaks. Use it when the user asks about a price or a minimum.

Input Schema

NameRequiredDescriptionDefault
widthInNoWidth in inches, 1 to 12.5. Default 3.
heightInNoHeight in inches, 1 to 12.5. Default 3.
quantityNoHow many patches. Default 100. Use 1 for a single patch.
patchTypeNoPatch type: embroidered (default), woven, chenille, printed, pvc-2d or pvc-3d. Iron-on, velcro and sew-on are backings on an embroidered patch, so use embroidered for those.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / patchType / enum
      Previous value: -[
-  "embroidered",
-  "woven",
-  "chenille",
-  "printed",
-  "pvc-2d",
-  "pvc-3d"
-]New value: +[
+  "embroidered",
+  "woven",
+  "chenille",
+  "printed",
+  "leather",
+  "pvc-2d",
+  "pvc-3d"
+]
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, and the description adds genuinely useful context beyond them: the returned price is the customer's final price rather than a starting figure, there is no minimum, quantity 1 returns sample pricing, default is to quote the price breaks, and custom backings/borders are confirmed within 2 business hours. It also discloses what the price already includes (artwork, pre-production sample, worldwide shipping).

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?

Purpose and output are front-loaded, and most sentences carry real information. A few are dense and comma-spliced (the quote/no-quote sentence and the price-breaks default), which slightly slows parsing but does not waste words.

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?

For a read-only pricing lookup with four optional, fully documented parameters and no output schema, the description covers everything an agent needs: what goes in, what comes back, the no-minimum rule, and the exception path for unlisted backings and borders.

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%, so the schema already documents all four parameters including the enum and ranges. The description only restates the input categories (type, size, quantity) and adds the behavioral detail that quantity 1 yields sample prices, which is closer to usage guidance than parameter semantics. Baseline 3 is appropriate.

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 – prices a custom patch from the live PatchDesign.AI production price table – and spells out the input/output contract (type, size, quantity in; per-patch and total USD out). It is clearly distinguishable from design_patch and edit_patch, which concern design rather than pricing.

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 when the user asks about a price or a minimum" gives a clear trigger, and the note that no quote is required unless a backing or border lacks a set price supplies a when-not condition. It does not name the sibling tools or state what to call instead for design work, so it stops short of full alternative routing.

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

All PatchDesign.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