Skip to main content
Glama
Sign In

Hoplix Print on Demand

by com.hoplix
OverviewDiscussionsAdmin

Search the Hoplix catalogue

list_products
Read-onlyIdempotent

Lists the blank products available on Hoplix (t-shirts, hoodies, mugs, bags, phone cases...) with product code, colours, sizes, base cost in EUR for front print and for front and back print, production days.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results (default 20)
offsetNoNumber of results to skip, for paging (default 0)
searchNoText to look for in product name or code (e.g. "hoodie", "mug")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that by disclosing the shape of the returned records — product code, colours, sizes, base cost in EUR split for front print vs front-and-back print, and production days — which matters because there is no output schema. It does not mention pagination behaviour or total-result counts.

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 sentence that front-loads the core action and then enumerates returned fields; nothing is redundant with the title. The parenthetical category list and the long field clause make it dense, but each clause carries information the agent needs since no output schema exists.

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 read-only, three-parameter listing tool with full schema coverage and rich annotations, this is nearly complete: it describes scope and return fields, which is the main gap a missing output schema creates. Minor omissions are pagination/total-count semantics and whether all catalogue items or only currently available ones are returned.

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%, with limit, offset and search each documented including defaults, maximums and examples. The description adds no parameter-level meaning beyond the schema, 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?

The description gives a specific verb and resource ('Lists the blank products available on Hoplix') and enumerates the categories covered, so an agent can tell this is a catalogue-browsing call rather than a single-item lookup. It does not explicitly name the sibling get_product as the alternative for fetching one product's details, so differentiation is left to inference from the names.

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 is implied by the content ('available on Hoplix', the search parameter's examples 'hoodie', 'mug'), so an agent can infer this is for browsing/searching the catalogue. There is no explicit statement of when to prefer it over get_product, no guidance on paging through large catalogues, and no exclusions.

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

All Hoplix Print on Demand 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