RetailHardHat

Get Site Lease Activity

get_site_lease_activity

Read-onlyIdempotent

Use this when working with RetailHardHat leases records in the connected organization. Read synchronized lease activity and refresh metadata. 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>"
    },
    "name": "get_site_lease_activity"
  }
}

Input Schema

Name	Required	Description	Default
`siteId`	Yes

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

C2.7/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. The description adds two useful pieces of context the annotations cannot carry: that the data is synchronized (staleness implications) and that approvals are administrator-configurable with business workflow approvals always applying. However, "refresh metadata" is ambiguous about whether the call has a side effect, which sits awkwardly against readOnlyHint=true.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the usage trigger, but the third sentence is generic MCP approval boilerplate that applies to nearly every tool and does not earn its place here.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. What remains missing is the one thing that matters for selection: how this differs from the other lease-related read tools and what the single required parameter must be.

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%: siteId is only typed as a UUID with a pattern, with no explanation of which site identifier source it must come from. The description does not mention siteId at all, so it fails to compensate for the gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Read synchronized lease activity and refresh metadata" gives a verb+resource, but "activity" and "refresh metadata" are vague and it never separates itself from closely named siblings such as list_site_leases, get_lease_sync_status, and refresh_leases. An agent can guess the domain but not the distinct scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use this when working with RetailHardHat leases records" is a domain statement, not a use condition. There is no when-not guidance and no mention of the sibling lease tools that would be the obvious alternatives.

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?