RetailHardHat

List Deals

list_deals

Read-onlyIdempotent

Use this when working with RetailHardHat deals records in the connected organization. List deals 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_deals"
  }
}

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

B3.1/5.0

Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful context about bounded pagination, search, and organization-level approval requirements, but does not explain result ordering or permission scoping beyond what annotations and schema already imply.

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 not bloated, but the first two sentences are largely redundant: 'Use this when working with...' followed by 'List deals in your organization.' The approval sentence adds behavioral context but makes the definition four sentences for a simple list tool.

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?

The description covers the core list operation, pagination/search support, and approval context, and the output schema means return values need not be described. It remains incomplete for a tool ecosystem of this size because it does not clarify when to choose list_deals over get_deal or other deal-related siblings.

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 only 33%, with meaningful documentation for id and siteId but not for limit, offset, search, or status. The description partially compensates by mentioning bounded pagination and search, but leaves the status filter and exact search semantics unexplained.

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 clear verb and resource: list deals in the organization. However, the opening phrase 'working with RetailHardHat deals records' is broad and does not distinguish this from sibling tools such as get_deal, create_deal, or update_deal.

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 gives no explicit when-to-use guidance against alternatives, no when-not conditions, and no routing advice such as using get_deal for a single record. The implied usage is only that this is a list operation.

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?