RetailHardHat

List Permits

list_permits

Read-onlyIdempotent

Use this when working with RetailHardHat permits records in the connected organization. List permits in your organization. Supports bounded pagination and search. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.

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

Input Schema

Name	Required	Description
`id`	No	Optional exact record UUID. Filters the authorized list to this record, without broadening permissions.
`limit`	No
`offset`	No
`search`	No
`siteId`	No	Optional RetailHardHat location UUID, not a location name. Resolve names with list_sites first.
`status`	No

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

C2.8/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, so safety is covered. The description adds the bounding of pagination and a caveat that MCP approval requirements are administrator-configurable while business workflow approvals always apply — useful context that annotations don't supply, though phrased generically.

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?

Front-loaded but the first two sentences overlap ('working with permits records' / 'List permits'), and the trailing approval-requirement sentence is boilerplate that reads as platform-wide policy rather than tool-specific guidance.

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?

With 6 optional parameters, low schema coverage, and a status string with no enum or documented values, the description leaves the agent guessing about filter semantics. The output schema existing lightens the return-value burden, but the input-side gaps remain unaddressed.

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 only 33% (only id and siteId are documented), so the description needs to compensate but does not: it never explains status matching semantics, search scope, or limit/offset bounds despite having 6 parameters. It only echoes that pagination and search exist.

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?

States a clear verb+resource: 'List permits in your organization.' The scope (organization-wide) is stated, but it does not distinguish itself from siblings like get_permit or list_permit_documents, so an agent must infer the difference.

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 opening 'Use this when working with RetailHardHat permits records' is essentially a restatement of the name, and no when-not-to-use case or alternative tool is named. 'Supports bounded pagination and search' implies usage but gives no guidance on choosing this over get_permit.

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?