RetailHardHat

Apply Project Budget Template

apply_project_budget_template

Apply a project_budget template to an existing project. Does not create the destination. 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": "apply_project_budget_template"
  }
}

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

A3.9/5.0

Behavior5/5

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

It discloses high-level behavioral traits regarding governance that are absent from the technical annotations. It warns the agent that complex approval workflows (MCP and business) will always apply, which is a major operational constraint.

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 uses only two sentences, both of which are high-impact and provide distinct pieces of information (what it does, and its constraints), making it efficient.

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 provides crucial non-functional context (approvals, existing destination), the description is technically incomplete as it lacks output expectations or detailed error conditions. However, given the complexity of the operation, the provided context is a minimum viable effort.

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

Parameters1/5

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

The schema description coverage is 0%, yet the description does not add meaningful semantic value to the parameters. It only explains the functional behavior and system constraints, failing to clarify what the `id` or `projectId` inputs fundamentally represent beyond their role in the action.

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 direct and clear, using a specific action ('Apply') on a specific resource ('project_budget template'). This clearly distinguishes it from other similar sibling tools like 'create_project_budget_template' or 'update_project_budget_template'.

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 provides a critical constraint: 'Does not create the destination,' meaning the target project must already exist. This guides the agent to use 'create_project' first if the project is missing, which is essential usage 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?