RetailHardHat

Create Budget Line Item

create_budget_line_item

Use this when working with RetailHardHat budgets records in the connected organization. Create a budget line item. Requires financial approval. 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": {
      "budgetId": "<budgetId>",
      "data": "<data>"
    },
    "name": "create_budget_line_item"
  }
}

Input Schema

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

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Goes well beyond annotations: discloses that no change occurs until a human approves the exact request in Settings > MCP and execute_approved_action is called, and that business-workflow approvals always apply. This is genuinely valuable behavioral context that the destructiveHint=false annotation does not convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is low-value filler before the actual purpose. The approval sentences earn their place, but front-loading is poor and the framing phrase could be removed without loss.

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?

The approval workflow is well covered and an output schema exists so return values need no explanation. However, for a tool with a complex nested `data` payload and zero schema descriptions, the total absence of parameter guidance leaves a material 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% and the description mentions no parameters at all. The `data` object is a large nested structure with categories, amounts, contingency fields, and enums that the agent must infer purely from schema shapes.

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?

States a specific verb+resource ("Create a budget line item") that is readily distinguishable from update_budget_line_item and create_budget_template_item. The lead sentence "working with RetailHardHat budgets records" is vague filler but the core purpose is unambiguous.

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?

The approval gating is explained, but there is no guidance on when to create a line item versus create_budget_template_item, apply_budget_template, or bulk_assign_budget_line_items. Usage is only implied by the tool name and approval prerequisites.

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?