RetailHardHat

List Rfps

list_rfps

Read-onlyIdempotent

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

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.4/5.0

Behavior4/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 context about bounded pagination, search, and approval requirements, including that business workflow approvals always apply.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded, with the core listing purpose stated immediately. There is some redundancy between the first two sentences, but it remains efficient overall.

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?

With an output schema and rich annotations present, the description does not need to explain return values or safety behavior. However, it remains incomplete on filter semantics and parameter usage, especially for status and search behavior.

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 low at 33%, and the description only broadly mentions bounded pagination and search. It leaves important filters such as status, and the precise meaning of search and pagination parameters, undocumented beyond the schema constraints.

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 specific verb and resource: listing RFP records in the connected organization. It is clear what the tool does, though it does not explicitly differentiate itself from sibling list tools such as list_rfis or list_bids.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives context for when to use the tool by referencing RetailHardHat RFP records, but it does not specify when not to use it or name alternatives. Usage is implied rather than fully guided.

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?