RetailHardHat

Create Task

create_task

Use this when working with RetailHardHat tasks records in the connected organization. Create task. Required fields are validated by the application. 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": {
      "data": "<data>"
    },
    "name": "create_task"
  }
}

Input Schema

Name	Required	Description	Default
`data`	Yes

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

C2.6/5.0

Behavior3/5

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

Annotations already establish this is a non-destructive, non-idempotent write with no external side effects, so the bar is lower. The description does add genuinely non-structured behavior: required-field validation happens server-side and creation may be gated by MCP approval settings plus mandatory business workflow approvals. However, it never says what a blocked/validated failure looks like or whether the task is created before approval.

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?

Three short sentences with no bloat, but the lead sentence is generic filler ("Use this when working with ... records in the connected organization") that pushes the actual operation and the approval caveat to the back. Front-loading what is created and what is required would earn more.

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

Completeness2/5

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

For a write tool with a deeply nested, entirely undocumented payload, the description omits which fields are required (siteId, title), how assignee/assigneeIds differ, and how this differs from create_project_task. An output schema exists so return values need not be explained, but the invocation-side gaps are significant.

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 single `data` object nests ~18 properties (siteId, title, assignee vs assigneeIds, type, priority, dates, etc.) with no documentation anywhere. The only hint is "Required fields are validated by the application," which neither names siteId/title nor explains the ambiguous fields an agent is most likely to misuse.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Create task" names a verb and resource, but it largely restates the tool name and title, and the added phrase "working with RetailHardHat tasks records in the connected organization" is generic. Critically, it does not distinguish this from the sibling create_project_task, which an agent must choose between.

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

Usage Guidelines2/5

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

"Use this when working with RetailHardHat tasks records" gives no real when-to-use condition, no exclusions, and no pointer to alternatives such as create_project_task, apply_task_template, or create_task_template. The agent is left to infer the correct tool from name alone.

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?