RetailHardHat

Update Project Task

update_project_task

Destructive

update a general-project task, not a site task. Supports hierarchy, assignment, status, priority and due dates; no completion timestamp or actor overrides. 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": {
      "projectId": "<projectId>",
      "projectTaskId": "<projectTaskId>",
      "data": "<data>"
    },
    "name": "update_project_task"
  }
}

Input Schema

Name	Required	Description	Default
`data`	Yes
`projectId`	Yes
`projectTaskId`	Yes

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare this as destructive and non-idempotent, so the description doesn't need to repeat that. It adds useful context beyond annotations: no completion timestamp or actor overrides, and that approval requirements are organization-configurable while business workflow approvals always apply.

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?

Three tight sentences with the scope distinction front-loaded. No filler or repetition; every sentence contributes useful information.

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

Completeness4/5

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

Given the mutation complexity and the presence of an output schema, the description covers the key scope and approval caveats well. It still leaves gaps around partial-update semantics and the full shape of the data object, but these are partially inferable from the schema.

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

Parameters3/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. It lists several updatable fields (hierarchy, assignment, status, priority, due dates) but omits title, description, the data wrapper, null semantics, and partial-update behavior. Partial compensation is present but incomplete.

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 states a specific verb (update) and resource (general-project task), and immediately distinguishes it from a site task. An agent can identify the right tool without needing to compare schemas.

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 clearly excludes site tasks, which is an important routing condition among the many update_* siblings. However, it does not explicitly name the alternative tool for site tasks, so the guidance is clear but not fully prescriptive.

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?