RetailHardHat

Refresh Purchase Tracking

refresh_purchase_tracking

Use this when working with RetailHardHat purchase_lists records in the connected organization. Refresh tracking using configured carrier integrations. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.

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": {
      "siteId": "<siteId>",
      "purchaseItemId": "<purchaseItemId>"
    },
    "name": "refresh_purchase_tracking"
  }
}

Input Schema

Name	Required	Description	Default
`siteId`	Yes
`purchaseItemId`	Yes

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A3.6/5.0

Behavior5/5

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

Adds substantial context beyond annotations: no mutation occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. It also notes that MCP approval requirements are configurable and that business workflow approvals always apply, which is critical for an agent to understand before invoking a non-readOnly operation.

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?

The description is reasonably front-loaded and appropriately sized for a tool with approval semantics. It is mostly efficient, though the first sentence is broad and the approval details could be slightly tighter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The approval workflow and business context are well covered, and an output schema exists so return values need not be described. However, for a two-parameter mutation with 0% schema description coverage, the missing parameter semantics leave a significant gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and both siteId and purchaseItemId are required UUIDs, but the description does not explain what either parameter identifies. It mentions purchase_lists records generally without mapping parameters to sites or purchase items.

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 (refresh) and resource (purchase tracking) and ties it to RetailHardHat purchase_lists records and carrier integrations. It is clear what the tool does at a high level, though it does not explicitly distinguish itself from related purchase-item or tracking-event siblings.

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?

Provides a usage context ('when working with RetailHardHat purchase_lists records'), but does not state when to avoid it or name alternatives such as listing purchase tracking events or updating purchase items. The approval flow is explained, but tool-selection guidance is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All RetailHardHat tools Inspect

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

Need Help?