RetailHardHat

Attach Daily Log Photo

attach_daily_log_photo

Use this when working with RetailHardHat field_operations records in the connected organization. Attach an owned uploaded photo to a daily log. 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": {
      "dailyLogId": "<dailyLogId>",
      "data": "<data>"
    },
    "name": "attach_daily_log_photo"
  }
}

Input Schema

Name	Required	Description	Default
`data`	Yes
`dailyLogId`	Yes

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description goes far beyond the basic `destructiveHint: false` annotation by explaining the core operational mechanism. It informs the agent that no change is immediate, requiring human approval via 'execute_approved_action', which is vital execution knowledge.

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?

The description is highly efficient. The first sentence establishes the context, and the second sentence handles the critical workflow behavior in a single, clear statement, with zero superfluous language.

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

Completeness5/5

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

The definition provides every piece of context needed for correct invocation: the target record type,the input requirement (photo attachment), and the external operational constraints (approval workflow). This makes it highly complete.

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?

With 0% schema description coverage, the burden falls on the text. The description successfully frames the context (attaching a photo to a log), but since it adds no semantic value to the complex structure of the `data` object itself, the baseline score of 3 is appropriate.

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 purpose is perfectly clear: to attach an owned uploaded photo to a daily log. It explicitly names the resource and the specific action, distinguishing it from general document or project attachment tools.

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 defines the scope as 'RetailHardHat field_operations records in the connected organization.' While it doesn't explicitly name sibling tools to avoid (like other `attach_` tools), the strong domain focus on 'daily log' and 'photo' provides sufficient guidance for selection.

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?