RetailHardHat

Get Opening Record Details

get_opening_record_details

Read-onlyIdempotent

Use this to inspect the authorized location, task or permit behind a RetailHardHat opening-risk signal. Requires the selected record's corresponding module scope and current route permissions. It is read-only and does not certify readiness or grant access to other modules.

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": {
      "recordType": "<recordType>",
      "id": "<id>"
    },
    "name": "get_opening_record_details"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`recordType`	Yes

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 the read-only, idempotent, non-destructive, closed-world profile. The description adds meaningful authorization context (module scope and route permissions) and boundary conditions (does not certify readiness or grant access to other modules), though it does not discuss error behavior or rate limits.

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?

Three compact sentences, front-loaded with the purpose, then prerequisites, then scope boundaries. No filler or redundant repetition of the tool name.

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 presence of an output schema and rich annotations, the description covers purpose, authorization prerequisites, and scope limitations well enough. It is slightly incomplete because it does not address sibling alternatives or clarify parameter semantics.

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, but it only partially does so. It hints at the recordType concept via 'location, task or permit' (with 'location' not exactly matching the enum value 'site') and does not explain the id parameter at all.

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 states a specific verb (inspect) and resource (record details) tied to RetailHardHat opening-risk signals, and it names the record types (location, task, permit). It does not explicitly differentiate itself from nearby siblings such as get_site, get_task, get_permit, or identify_opening_blockers.

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 gives a clear usage context ('inspect ... behind a RetailHardHat opening-risk signal') and states prerequisites around module scope and route permissions. It does not explain when not to use this tool or name alternative tools for related lookup needs.

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?