RetailHardHat

Create Smartshifts Linked Location

create_smartshifts_linked_location

Create/link this site's location in the existing smartshifts connection. Review all transmitted fields; external system changes are not automatically rolled back. 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_smartshifts_linked_location"
  }
}

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

A3.7/5.0

Behavior5/5

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

The description goes far beyond the standard annotations. It highlights crucial behavioral traits like 'external system changes are not automatically rolled back,' which informs the agent about the permanence and high risk of the mutation, and describes the approval workflows involved.

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 three sentences are highly efficient, focusing solely on defining the scope, risk, and procedural requirements of the operation without unnecessary fluff.

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 that this is a high-risk mutation tool linked to external systems, the inclusion of rollback warnings and workflow requirements makes the definition contextually strong. It is only held back from a 5 by the total lack of parameter documentation.

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

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 0%, meaning the input parameters are entirely undocumented. Despite this being a critical failure in documentation structure, the description fails to add any meaningful semantic context or explanation for the required fields beyond their operational existence.

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 description clearly identifies the action (create/link) and the specific resource/context (this site's location in the smartshifts connection). While it doesn't name a sibling tool to differentiate from, the mention of 'smartshifts' provides necessary context.

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?

It implies usage when integrating a site's location into an existing smartshifts connection. However, it does not explicitly state when this tool should be used versus other 'create' or 'update' tools in the MCP hierarchy.

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?