Softwear Prints

Search products

search_products

Read-onlyIdempotent

Searches the Softwear Prints catalogue of textiles and promotional items that can be printed or embroidered. Supports free text and filters for category, brand, colour, size, target group, material, certification and price. Returns name, brand, article number, unit price (net and gross), colours and a link to the product page.

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

Input Schema

Name	Required	Description	Default
`page`	No
`size`	No	Sizes, e.g. ['XL', '3XL'].
`sort`	No		relevance
`brand`	No	Brand names, e.g. ['HAKRO'].
`color`	No	Colour names in German or English, e.g. ['navy'] or ['rot'].
`query`	No	Free-text search, e.g. 'polo shirt organic cotton'.
`gender`	No	Target group, e.g. ['Damen'], ['Herren'], ['Kinder'], ['Unisex'].
`category`	No	Category slug or id as returned by list_categories.
`language`	No	Language of product names in the result.	de
`material`	No	Material names, e.g. ['Baumwolle'].
`page_size`	No	Products per page. With a colour filter a page can hold more or fewer products.
`price_max`	No	Maximum unit price in EUR.
`price_min`	No	Minimum unit price in EUR.
`price_basis`	No	Whether price_min and price_max include German VAT (gross) or not (net).	gross
`certification`	No	Certifications, e.g. ['Oeko-Tex 100'].

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 14, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful context the annotations cannot: the supported filter dimensions and, importantly, the shape of the result (name, brand, article number, net/gross unit price, colours, product link) in the absence of an output schema.

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?

Two sentences, front-loaded with purpose, then filters, then return shape. No filler, though the filter enumeration in the middle sentence is a dense list that largely mirrors the schema.

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?

For a 15-parameter, all-optional search tool with no output schema, the description covers what the tool covers and what it returns, which is the main gap an agent would otherwise hit. It omits pagination behaviour (page/page_size interactions) and the 5-item cap on array filters, but those are documented in the schema.

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 87%, so the schema already documents nearly every parameter (sizes, brand, colour language variants, price basis, page_size caveat). The description's enumeration of filter categories restates the schema's capability set at a glance rather than adding syntax, defaults, or semantics beyond it, so the baseline 3 applies.

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?

Specific verb (searches) plus resource (Softwear Prints catalogue of textiles and promotional items), with the domain scope stated up front. An agent can distinguish it from get_product (single-item retrieval) and list_categories (category enumeration) without opening any schema. It also names the filtering dimensions the tool supports.

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

Usage Guidelines3/5

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

Usage context is implied rather than stated: the tool is clearly the catalogue-browsing entry point, and the category parameter description nudges the agent to call list_categories first. However, there is no explicit when-to-use vs. get_product guidance and no statement of prerequisites or exclusions for the 15 filters.

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

All Softwear Prints 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?