AI Separations

Estimate screens (free)

estimate_screens

Read-onlyIdempotent

FREE, no key needed. Analyze artwork for screen printing: how many spot-color screens it needs, the detected ink colors (with named ink matches), whether it's flat/vector or photographic, and whether screen printing or DTF is the better process. Use this first on any logo or design.

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

Input Schema

Name	Required	Description
`garment`	No	Shirt the art prints on: "dark" (black, default), "light" (white), a color name (Navy, Royal, Red, Maroon, Forest, Gold, Heather Grey, Charcoal, ...) or a hex like "#1f2a44". The separation is solved against that exact shirt color.
`image_b64`	No	Base64 (or data URL) of the artwork — alternative to image_url
`image_url`	No	Public http(s) URL of the artwork (PNG/JPG, max 12 MB)
`underbase`	No	Print a white underbase (default: on for shirts darker than mid-grey)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so the safety profile is covered. The description adds genuinely new operational context beyond them: it is free and requires no API key, which is behavior an agent needs before deciding to call it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, with the highest-value qualifier (FREE, no key needed) front-loaded. The output enumeration is dense but every clause carries distinct information.

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?

With no output schema, the description correctly compensates by summarizing the return contents, and it covers prerequisites and usage timing for a 4-param read-only tool. It stops short of describing response shape or error/fallback behavior when the image cannot be analyzed.

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 each parameter (garment, image_b64, image_url, underbase) is well documented in the schema itself. The description does not add any parameter-level meaning beyond that, so the baseline 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?

States a specific verb (analyze) and resource (artwork for screen printing) and enumerates the concrete outputs: screen count, ink colors with named matches, flat/vector vs photographic classification, and screen-print vs DTF recommendation. It is clearly distinguishable from credit/pricing siblings, but never names the closest sibling (separate_image), so full sibling differentiation is missing.

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 this first on any logo or design" gives explicit placement in the workflow and, combined with "FREE, no key needed," tells the agent a prerequisite-free entry point. There are no stated when-not conditions or named alternatives, which keeps it 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.

All AI Separations 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?