RetailHardHat

List Site Documents

list_site_documents

Read-onlyIdempotent

Use this when working with RetailHardHat documents records in the connected organization. Read site document 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": "list_site_documents"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No
`search`	No
`siteId`	Yes

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

C2.4/5.0

Behavior3/5

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

The annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful approval context ('MCP approval requirements are configurable... business workflow approvals always apply'), but it does not explain pagination behavior or the distinction between reading metadata and reading document content.

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?

The description is short, but the first sentence is awkward and redundant with the title, and the approval sentence reads as boilerplate. The actual purpose ('Read site document metadata') is not front-loaded as clearly as it could be.

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

Completeness2/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. However, for a list tool with pagination and search parameters, the description leaves key invocation details undocumented and does not help the agent distinguish this operation from related document tools.

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

Parameters1/5

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

Schema description coverage is 0% and there are four parameters, including siteId, limit, offset, and search. The description does not explain any of these parameters, so it fails to compensate for the missing schema documentation.

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?

The description says to 'Read site document metadata,' which identifies a verb and resource, but it does not clearly state that this is a list operation or how it differs from siblings such as read_site_document or list_project_documents. The opening phrase about 'RetailHardHat documents records' is vague and largely restates the tool title.

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 phrase 'Use this when working with RetailHardHat documents records' is too generic to guide selection. It does not compare this tool with read_site_document, list_project_documents, or other document-related siblings, nor does it state when to prefer this list tool over those 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?