RetailHardHat

Submit Rfp Approval Request

submit_rfp_approval_request

Submit an existing rfp to the configured business approval flow. Does not approve it. 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": {
      "data": "<data>"
    },
    "name": "submit_rfp_approval_request"
  }
}

Input Schema

Name	Required	Description	Default
`data`	Yes

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A3.9/5.0

Behavior4/5

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

The description adds significant behavioral value beyond annotations by clarifying the precise nature of the action—submission rather than completion or approval. This prevents an agent from misusing the tool to expect an immediate 'Approved' status, even though `readOnlyHint` is false.

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 concise, consisting of two focused sentences. It front-loads the core function and its most important behavioral caveat (not approving it) immediately.

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?

While it defines the action well, it is incomplete regarding operational data. Given the 0% schema coverage, it should clarify that the input entity must already exist and that the required `data` object must contain a valid `entityId` pointing to that pre-existing RPF.

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 coverage is 0%, meaning the description is responsible for defining the inputs. It fails to explain the purpose of the primary parameters (`entityId` or `notes`) or what validation is expected on the `entityId` beyond the schema structure itself. It adds minimal semantic value to the input structure.

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 is highly specific: it submits an *existing* RPF to a configured approval flow. Crucially, it explicitly states, 'Does not approve it,' which effectively distinguishes it from other tools in the submission/approval family, preventing false positive routing.

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?

The description provides clear operational context by mentioning that MCP requirements are configurable and that business workflow approvals are mandatory. This sets expectations for the AI agent regarding the outcome (workflow initiation) versus immediate decision-making.

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?