RetailHardHat

Update Rfi

update_rfi

Destructive

Use this when working with RetailHardHat rfis records in the connected organization. Update allowed fields of rfi. No change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called. 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": {
      "id": "<id>",
      "data": "<data>"
    },
    "name": "update_rfi"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`data`	Yes

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

Behavior4/5

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

The description adds important behavioral context beyond annotations: no change occurs until human approval via Settings > MCP and execute_approved_action, and approval requirements are administrator-configurable with business workflow approvals always applying. It aligns with destructiveHint=true and idempotentHint=false without contradicting them.

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 reasonably concise and front-loads usage context followed by the update operation and approval requirements. There is minor redundancy in 'RetailHardHat rfis records' but no wasted sentences.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The approval workflow is well covered, which is important for this mutation tool, and an output schema exists. However, with 0% schema description coverage and a nested data object containing many fields, the description omits what fields are updatable and how to form the request, leaving a significant completeness gap.

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 0%, so the description must compensate for undocumented parameters, but it only says 'Update allowed fields of rfi' without explaining the required 'id' or the structure and meaning of the 'data' object's many fields. It adds almost no semantic value beyond the schema.

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: 'Update allowed fields of rfi.' It is clear this is an update operation on RFI records, though it does not differentiate itself from sibling tools like update_rfi_comment or get_rfi.

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 only usage guidance is the generic 'Use this when working with RetailHardHat rfis records in the connected organization.' There is no explicit when-to-use, when-not-to-use, or alternative selection guidance against the many sibling RFI 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?