hsh_check_order
FREE. Check fulfillment status of a paid order by its order reference (HSH-XXXXXXXX).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| order_ref | Yes | The order reference, e.g. HSH-1A2B3C4D |
HSH Data-on-Demand
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- Added
TDQS
A3.6/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It notes the tool is free and checks status, but fails to disclose behavioral traits such as what happens if the order is not found, rate limits, or data freshness. This is minimal disclosure for a read operation.
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?
The description is extremely concise at one sentence plus 'FREE.', with all information front-loaded. Every word earns its place without superfluous text.
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's simplicity (one parameter, no output schema, no nested objects), the description covers core functionality and parameter format. It could mention the return behavior for missing orders, but overall it is adequately complete for a straightforward lookup 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 coverage is 100% with one parameter 'order_ref' described as 'The order reference, e.g. HSH-1A2B3C4D'. The description adds the pattern 'HSH-XXXXXXXX' but adds minimal value beyond the schema, so baseline 3 is appropriate.
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?
The description clearly states the verb 'Check' and the resource 'fulfillment status of a paid order', using the required order reference format 'HSH-XXXXXXXX'. It distinguishes this tool from siblings like 'hsh_check_quote' and 'hsh_check_subscription' by specifying it is for order fulfillment.
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?
The description indicates the tool is free and shows the expected order reference format, implying usage when you have a paid order. However, it does not provide explicit guidance on when to use it versus alternatives, nor does it mention prerequisites or exclusions.
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
B3.3/5.0
Disambiguation4/5
Most tools have distinct purposes, but some closely related tools (e.g., hsh-b2b-*, hsh-esg-* variants) could cause confusion. Descriptions help differentiate, but an agent might still misselect similar products.
Naming Consistency3/5
Naming convention is mixed: some tools use hyphens (hsh-b2b-contact), others use underscores (hsh_broker_data_request). While mostly readable, the inconsistency could be confusing for agents expecting a uniform pattern.
Tool Count3/5
32 tools is on the high side for a single server, but given its purpose as a data marketplace, the large number reflects a wide catalog. However, it may be overwhelming for agents to navigate.
Completeness3/5
Covers many data domains but has obvious gaps (e.g., weather, social media). The inclusion of custom data request tools (hsh_describe_data_need, hsh_broker_data_request) mitigates these gaps, allowing agents to request missing data.