RetailHardHat

Create Project Note

create_project_note

Use this when working with RetailHardHat projects records in the connected organization. Add a project note. 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": {
      "projectId": "<projectId>",
      "data": "<data>"
    },
    "name": "create_project_note"
  }
}

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

B3.3/5.0

Behavior4/5

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

The description adds substantial context beyond the annotations: it explains the deferred-execution model ('No change occurs until a human approves the exact request ... and execute_approved_action is called') and that approval requirements are configurable per organization. It does not address duplicate handling, failure modes, or the fact that non-idempotentHint=true means repeat calls create separate notes.

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 tool's actual action ('Add a project note') is buried second behind a generic RetailHardHat boilerplate sentence. The approval-administration sentence is useful but verbose, and the core operation should lead.

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?

An output schema exists, so return values need not be described. However, for a mutation with a nested payload and zero parameter documentation, the definition leaves the agent guessing about what goes into data and under what conditions the create fails or duplicates.

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 says nothing about projectId, data.content, or the optional data.title. With a nested object and a required UUID parameter, the description should at minimum explain the note body fields and the 10000-character limit it is working within.

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?

The sentence 'Add a project note' gives a specific verb and resource, and the surrounding boilerplate names the domain (RetailHardHat projects records). It is distinguishable from the sibling update_project_note by the 'add' verb, though the tool never names that sibling explicitly.

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?

'Use this when working with RetailHardHat projects records in the connected organization' is a scope hint rather than a real when-to-use rule, and no exclusions or alternatives are given. The one genuinely actionable guideline is the requirement to follow up with execute_approved_action after human approval.

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?