RetailHardHat

Compare Site Bids

compare_site_bids

Read-onlyIdempotent

Use this when comparing recorded contractor bids for a RetailHardHat location UUID. Groups by category, project, and RFP; shows amounts and differences from each group's lowest eligible amount. Do not use for unrelated insurance quotes or automatically select, approve, or award a contractor.

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

Input Schema

Name	Required	Description	Default
`siteId`	Yes	RetailHardHat location UUID, not a location name. Find the ID with list_sites if needed.

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds output semantics — grouping by category/project/RFP and differences from each group's lowest eligible amount — plus an explicit no-side-effects caveat. It does not mention pagination or data-completeness caveats.

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

Conciseness5/5

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

Two tight sentences: the positive use case and grouping behavior are front-loaded, followed by the exclusion clause. Nothing is redundant or padded.

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

Completeness4/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 needn't be spelled out, and annotations cover the safety profile. The description supplies grouping logic and scope exclusions, leaving only minor gaps like result ordering or behavior when a group has no eligible amount.

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 100%, and the schema already documents siteId as a UUID with a find_sites hint. The description merely repeats that a location UUID is required, adding no format or edge-case detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb (compare) plus a precisely scoped resource (recorded contractor bids for a RetailHardHat location UUID) and states how results are organized. It is clearly differentiated from siblings like list_bids or get_bid_details, which retrieve rather than compare.

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

Usage Guidelines5/5

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

It states an explicit trigger ('Use this when comparing recorded contractor bids...') and explicit exclusions ('Do not use for unrelated insurance quotes or automatically select, approve, or award a contractor'), steering agents away from award/approval 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?