RetailHardHat

Unlink Task Budget Line Item

unlink_task_budget_line_item

Destructive

unlink a site task and a budget line item from the same site. Does not change budget amounts or approve the budget. 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": {
      "taskId": "<taskId>",
      "lineItemId": "<lineItemId>"
    },
    "name": "unlink_task_budget_line_item"
  }
}

Input Schema

Name	Required	Description	Default
`taskId`	Yes
`lineItemId`	Yes

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A4.7/5.0

Behavior5/5

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

While annotations mark it as destructive, the description adds critical operational context: it clarifies that the budget amounts are unchanged and details the specific approval requirements (configurable MCP vs. fixed business workflow). This is valuable behavioral insight.

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?

The two sentences are highly efficient. The first is front-loaded with the action, and the second provides necessary behavioral constraints and governance, making perfect use of the limited space.

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

Completeness5/5

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

Given the simplicity of the schema (2 UUID parameters) and the strong existing annotations, the description provides all necessary semantic and operational guardrails for a well-formed invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Since schema description coverage is 0%, the description must compensate. It adds the semantic constraint that the task and line item must be 'from the same site,' a vital contextual link not provided by the UUID schemas alone.

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 tool clearly defines its function: 'unlink a site task and a budget line item.' It distinguishes the action from budget modification or approval workflows.

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?

It guides usage by stating what the tool does *not* do ('Does not change budget amounts or approve the budget'), which helps delineate its scope relative to other potential budget management 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?