RetailHardHat

Create Project Task

create_project_task

create 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>",
      "data": "<data>"
    },
    "name": "create_project_task"
  }
}

Input Schema

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

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover safety (write, non-idempotent, non-destructive). The description adds real context beyond that: which fields cannot be overridden ('no completion timestamp or actor overrides') and that approval requirements are admin-configurable while business workflow approvals always apply. This is meaningful behavior an agent needs before calling.

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?

Purpose and the site-task distinction are front-loaded, and the three clauses are dense but non-redundant. Slightly packed, but every clause earns its place.

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?

With an output schema present, return values needn't be explained, and the approval/behavioral notes fill the main non-schema gap. Only mild shortfall is incomplete optional-parameter meaning, but overall adequate for a 2-param create tool.

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 carry the load. It maps well to several nested fields (hierarchy=parentId, assignment=assignedToUserId, status, priority, dueDate), which is genuinely useful, but leaves projectId, title, and description unexplained and gives no format/UUID guidance.

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?

States a specific verb (create) and resource (general-project task) and immediately distinguishes it from the sibling create_task by clarifying 'not a site task.' An agent can route correctly without opening either schema.

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?

Explicitly scopes usage with 'not a site task,' which routes the agent to the site-task sibling for that case. Does not spell out broader exclusions, but the primary alternative is named, so it clears the 'no exclusions' bar.

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?