RetailHardHat

Get Operations Dashboard

get_operations_dashboard

Read-onlyIdempotent

Use this to review RetailHardHat retail-rollout operations in one place: budget overruns, opening risks, contractor bids for a selected location, and this connection's pending approvals. Returns authorized panels, selectable locations, drill-down actions and explicit per-panel errors. Never infers access to ungranted modules, complete readiness or financial forecasts.

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

Input Schema

Name	Required	Description	Default
`siteId`	No	Optional RetailHardHat location UUID. Omit to inspect the organization's available records.

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already establish readOnly/idempotent/closed-world/non-destructive safety, so the description exceeds the lower bar by disclosing an authorization model ('Returns authorized panels ... Never infers access to ungranted modules'), per-panel error semantics, and explicit negative guarantees about readiness and forecasts. That is meaningful context beyond the annotations, though the return-shape portion overlaps the output schema.

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 dense sentences with the purpose front-loaded, followed by return shape and boundary guarantees. Every sentence earns its place with no filler or repetition of the name.

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

Completeness5/5

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

With an output schema present, return values need not be fully re-explained, yet the description summarizes them (panels, locations, drill-down actions, per-panel errors) and adds access-scope caveats. Nothing an agent needs to invoke a single-optional-param read tool correctly is missing.

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?

Only one optional parameter with 100% schema coverage, which already documents siteId as an optional UUID and the omit behavior. The description echoes 'for a selected location' but adds no syntax or edge-case detail beyond the schema, so baseline 3 applies.

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?

States a specific verb (review) and resource (RetailHardHat retail-rollout operations dashboard) and enumerates the exact content panels: budget overruns, opening risks, contractor bids, and pending approvals. This enumeration distinguishes it from the individual panel tools in the sibling set (e.g., summarize_budget_overruns, identify_opening_blockers, list_pending_approval_requests) as an aggregation entry point.

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?

The opening 'Use this to review ... in one place' gives a clear context for invocation as an overview tool. However, it never names an alternative or states when NOT to use it versus the granular sibling tools, leaving the agent to infer the routing from 'in one place'.

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?