Skip to main content
Glama
Sign In

Hoplix Print on Demand

by com.hoplix
OverviewDiscussionsAdmin

Get order status

get_order_status
Read-onlyIdempotent

Status, shipping code and tracking URL of an order, looked up by Hoplix order id or by the seller's own order reference (one of the two is required).

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

Input Schema

NameRequiredDescriptionDefault
testNoWith order_reference: true to search among test orders
order_idNoHoplix order id, or a TEST-... id
order_referenceNoThe seller's own order reference given when the order was created

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/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 fully covered. The description adds only the input-selection constraint; it says nothing about error behavior when an unknown id is supplied, though for a simple read tool that is a minor gap.

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?

One dense sentence with no filler, front-loaded with the returned fields and followed by the lookup mechanism. The parenthetical constraint is slightly buried at the end rather than stated first.

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 compensates by enumerating the returned fields, and with only three flat parameters the annotations carry the rest. Complete enough to call correctly, lacking only a note on failure modes for invalid ids.

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 coverage is 100%, so each parameter is already documented in the schema. The description's only added meaning is the mutual-exclusivity constraint ('one of the two is required'), which is genuinely useful but modest given the schema does the rest.

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 names a specific resource (an order) plus the exact fields returned — status, shipping code, tracking URL — and states the two lookup keys. It does not distinguish itself from the sibling get_order, which is the main gap.

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?

It implies usage by saying the lookup is by order id or seller reference and that one of the two is required, which is actionable context. However, it gives no guidance on when to prefer this over get_order or list_orders, 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