Skip to main content
Glama
Sign In

Hoplix Print on Demand

by com.hoplix
OverviewDiscussionsAdmin

Quote an order

quote_order
Read-onlyIdempotent

Calculates total and shipping cost of an order with the seller's prices and discounts, running the same checks as a real order (campaign products, sizes, colours, quantities, address). Nothing is saved and nothing is charged.

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": {
      "products": "<products>",
      "shipping_mode": "<shipping_mode>",
      "shipping_info": "<shipping_info>"
    },
    "name": "quote_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
productsYesProducts to order
shipping_infoYesDelivery address
shipping_modeYesShipping method

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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, but the description adds domain-level substance: the quote runs the identical validation set (campaign products, sizes, colours, quantities, address) and persists/charges nothing. It does not say what the response looks like — a priced quote object versus a validation-error list — which matters since there is no 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.

Conciseness5/5

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

Two sentences with zero filler, and the payoff clause ('nothing is saved and nothing is charged') is placed last for emphasis while the primary function leads. Every phrase — the price components, the check list, the no-side-effect guarantee — 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?

For a three-parameter tool with nested objects and no output schema, the description covers purpose, validated domains and side-effect profile adequately. The remaining gap is the response contract: whether a quote returns per-line prices, totals, shipping options, or validation errors, which an agent must know to interpret results.

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%, so all three parameters and their nested fields are already documented in the input schema. The description only echoes the validated domains (sizes, colours, quantities, address) without adding format, default or inter-field 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?

States a specific verb and resource ('calculates total and shipping cost of an order') and immediately scopes it as a dry run that mirrors a real order's checks. The closing 'nothing is saved and nothing is charged' implicitly but unambiguously separates it from create_order, which is the correct sibling to distinguish from.

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?

The description makes the use case clear: price and validate a basket before committing, using the same rules a real order would. It stops short of explicit routing guidance, e.g. telling the agent to call check_shipping_address first or to switch to create_order once the quote is accepted, and gives no when-not conditions.

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