RetailHardHat

Duplicate Budget

duplicate_budget

Duplicate a budget and its line items as a new version. Does not approve the copy. 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": {
      "budgetId": "<budgetId>"
    },
    "name": "duplicate_budget"
  }
}

Input Schema

Name	Required	Description	Default
`data`	No
`budgetId`	Yes

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Beyond the annotations, the description discloses two genuinely useful behaviors: the copy is not auto-approved, and approval requirements are org-admin configurable while business workflow approvals always apply. It still doesn't say what happens to permissions, status, or defaults of the new copy.

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?

Three short sentences, front-loaded with the core action, and the non-approval caveat immediately follows. The final sentence on approval configurability is slightly tangential but relevant to calling the tool correctly.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. However, for a mutation/duplication tool the description omits the naming/overwrite behavior and any permission prerequisites, and leaves the 'data' parameter entirely undocumented.

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% across 2 parameters, and the description does not mention either one. It implies budgetId is the source budget but never explains the nested 'data.name' option for naming the copy, so it fails to compensate for the schema gap.

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 plus the scope of the copy: 'Duplicate a budget and its line items as a new version.' It clearly distinguishes duplication from creation at a conceptual level, but never names the nearest siblings (create_budget, clone_budget_template, apply_budget_template) to disambiguate explicitly.

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

Usage Guidelines3/5

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

Usage is implied — duplicate an existing budget when you want a new version rather than creating one from scratch — but no when/when-not conditions or alternatives are given. The approval notes add operational context rather than routing guidance.

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?