hip_get_order
Status and USPS tracking for the paid order belonging to this job.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| job_handle | Yes |
Have It Printed
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.8/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the behavioral disclosure burden. It does state what the tool returns (status and USPS tracking), which is useful, but it does not describe side effects, error behavior, prerequisites, or response details. Acceptable for a getter, but not rich.
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 short sentence with no filler. The output focus is front-loaded, and every word contributes meaning.
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?
Given the tool has only one required parameter, no output schema, and no annotations, the description covers the essential context: what is returned and to which job it applies. It could mention what happens when no paid order exists, but this is a minor gap for such a simple tool.
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 0%, so the description must compensate. It partially does by linking the sole parameter to 'this job', making it clear that job_handle identifies the job whose paid order is being queried. It does not define the handle format or how to obtain it, but the single self-explanatory parameter keeps this adequate.
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 clearly identifies the resource: status and USPS tracking for the paid order belonging to a job. It is distinct from sibling tools like hip_get_checkout_status because it refers to the paid order, not the checkout process. It lacks an explicit verb but the intent is unmistakable.
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 phrase 'for the paid order belonging to this job' gives clear context: use this when you need order-level status or USPS tracking after payment, tied to the job identified by job_handle. It does not explicitly contrast with alternatives, but the scope is clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.8/5.0
Disambiguation4/5
Most tools are clearly distinct by resource and action, such as create_job vs update_job or complete_payment vs create_checkout. However, hip_quote and hip_prepare_payment both return pricing information and could be confused at first glance; the descriptions do clarify their different purposes, but an explicit warning is needed to keep them apart.
Naming Consistency5/5
All tools follow the same hip_ prefix with verb_noun snake_case naming, such as hip_create_job, hip_get_order, and hip_complete_payment. This makes the toolset predictable and easy to navigate.
Tool Count5/5
Ten tools is well-scoped for a print-and-mail service. Each tool covers a necessary part of the workflow—job creation, document upload, quoting, payment, and order tracking—without unnecessary duplication or bloat.
Completeness4/5
The core lifecycle is well covered: create and update a job, upload documents, quote, pay via autonomous or checkout flows, check payment status, and retrieve order tracking. Minor gaps exist, such as no explicit cancel/delete job or a pre-payment job status retrieval tool, but agents can likely work around these.