RetailHardHat

Decide Bid Approval Request

decide_bid_approval_request

Record the current human user's explicit approve/reject decision for a bid. Requires exact-change review and being an assigned current-step approver. Amount ceilings restrict approvals, not rejections; subsequent approval steps still apply. 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": {
      "requestId": "<requestId>",
      "data": "<data>"
    },
    "name": "decide_bid_approval_request"
  }
}

Input Schema

Name	Required	Description	Default
`data`	Yes
`requestId`	Yes

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A4/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing authorization requirements (assigned current-step approver), the asymmetry that ceilings restrict approvals but not rejections, that subsequent approval steps still apply, and that org-level MCP approval config may layer on top. It does not state what happens on success or failure, keeping it from a 5.

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?

Front-loads the core action in the first sentence and each subsequent sentence adds a distinct constraint. Dense but largely waste-free; the final MCP-approval sentence is slightly tangential.

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?

For a workflow-mutation tool with an output schema (so return values needn't be explained), the description covers the key authorization, ceiling, and workflow-step constraints an agent needs. Some ambiguity remains about failure modes and the requestId target.

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?

With 0% schema description coverage and a nested data object, the description only implies the approve/reject action and says nothing about requestId (which request it identifies) or the notes field. It leaves both parameters largely undocumented.

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?

States a specific verb and resource ('Record the current human user's explicit approve/reject decision for a bid') and names 'bid' to distinguish it from the sibling decide_budget/invoice/rfp_approval_request tools. An agent can identify the operation without opening the schema.

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

Usage Guidelines4/5

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

Provides clear preconditions for use ('Requires exact-change review and being an assigned current-step approver') and clarifies the ceiling logic. It does not explicitly route to alternatives like submit_bid_approval_request or get_bid_approval_request, so it stops short of a 5.

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?