RetailHardHat

Refresh Leases

refresh_leases

Use this when working with RetailHardHat leases records in the connected organization. Refresh this organization's mapped sites from LeaseCommand. Requires an existing integration and human approval; does not edit the source leases. 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

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare it is a non-read-only, non-destructive, non-idempotent operation. The description adds real value beyond that: it scopes the side effects ('does not edit the source leases'), states that nothing changes until approval, and describes the approval mechanism and its configurability. It does not say what local records get overwritten on refresh, which is the main remaining 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?

The approval and safety constraints are front-loaded and each sentence carries information. The lead-in 'Use this when working with RetailHardHat leases records in the connected organization' is the weakest sentence and delays the actual action by one line.

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 zero params and an output schema present, the description covers what it must: prerequisites, approval gating, and the boundary of what the operation touches. It is only incomplete in failing to contrast with preview_leasecommand_sync and in not indicating what state changes locally after a successful refresh.

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

Parameters4/5

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

The tool takes zero parameters and the schema is empty with additionalProperties false, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter detail is missing.

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 second sentence gives a specific verb and resource: 'Refresh this organization's mapped sites from LeaseCommand.' However, the opening sentence ('Use this when working with RetailHardHat leases records') is vague filler, and the description never distinguishes this from the obvious sibling preview_leasecommand_sync, which an agent would need to choose between.

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?

It states the preconditions clearly (existing LeaseCommand integration, human approval) and routes the agent into the correct follow-up workflow (approve in Settings > MCP, then call execute_approved_action). It stops short of naming preview_leasecommand_sync as the read-only alternative, which is the most likely sibling confusion.

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?