RetailHardHat

Get Site Document Visibility

get_site_document_visibility

Read-onlyIdempotent

Read vendor portal visibility. Sharing changes require explicit review. 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>",
      "documentId": "<documentId>"
    },
    "name": "get_site_document_visibility"
  }
}

Input Schema

Name	Required	Description	Default
`siteId`	Yes
`documentId`	Yes

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A3.5/5.0

Behavior5/5

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

The description adds critical operational context—namely that sharing changes require explicit review and that MCP approval requirements are configurable. This business logic is vital context that goes far beyond the standard safety hints in the annotations.

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?

It is concise, but the two sentences are dedicated almost entirely to describing underlying business processes rather than the function or parameters of the API call itself.

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?

While it is complete in describing the *system constraints* of visibility (the approval matrix), it is incomplete in terms of functional instruction for the agent (e.g., does this return boolean true/false or a detailed status object?).

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?

The schema provides the only semantic definitions for siteId and documentId. Since the schema coverage is 0%, the description fails to add any meaningful meaning or constraints to the input parameters.

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 title and first sentence clearly state the function ('Read vendor portal visibility'). While it is specific to 'visibility,' it does not clearly distinguish between this and 'reading' the document content itself, relying on the tooling context.

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?

The description focuses entirely on the system's policy requirements (approval workflows) rather than providing clear guidance on *when* or *how* to use this specific read operation versus other related tools.

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?