Skip to main content
Glama
Sign In

Hoplix Print on Demand

by com.hoplix
OverviewDiscussionsAdmin

Get product details

get_product
Read-onlyIdempotent

Full details of one catalogue product: description, colours, sizes, base costs, production days, printable area, pixels needed for the artwork, weight, and the products that can be added to the same campaign.

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": {
      "product_code": "<product_code>"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_codeYesCatalogue product code (e.g. "maglietta-unisex")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by enumerating the fields returned (costs, production days, printable area, pixel requirements, add-ons), which matters because no output schema exists.

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?

One front-loaded sentence identifying scope followed by a compact field list; nothing is redundant and the enumeration substitutes for the missing output 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 single-parameter read tool with rich annotations and no output schema, the description covers purpose and return contents adequately. It stops short of describing what happens with an invalid or unknown product code.

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 the single product_code parameter already carries an example, so the description adds no further semantics such as format validation or lookup failure behaviour. 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-resource pair ("Full details of one catalogue product") and enumerates the returned fields, so the agent knows exactly what it fetches. It does not name the sibling list_products as the alternative, which keeps it short of a 5.

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 only implied: the required product_code and the word "one" suggest it is the follow-up to listing products, but there is no explicit when-to-use or when-not-to-use the sibling tools, and no note about behaviour on an unknown code.

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