RetailHardHat

Create Credentialcamp Linked Location

create_credentialcamp_linked_location

Create/link this site's location in the existing credentialcamp 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_credentialcamp_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

B3.4/5.0

Behavior4/5

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

Annotations already declare this as a non-read-only, non-idempotent, non-destructive mutation. The description adds substantive behavior beyond annotations: transmitted fields should be reviewed, external system changes are not automatically rolled back, and business workflow approvals always apply.

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?

The description is three sentences and front-loads the purpose before the warnings. The approval sentence is slightly boilerplate but relevant, and no major text is wasted.

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?

For a mutation touching an external system, the description covers purpose, irreversibility, and approvals, and an output schema exists. However, with completely undocumented nested parameters, it leaves field meaning and create-versus-link semantics under-specified.

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?

The schema has one nested 'data' object with six properties and 0% schema description coverage. The description says to 'review all transmitted fields' but explains none of them, leaving siteId, name, address, city, state, and externalId without semantic guidance beyond their names.

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 names a specific verb ('Create/link'), the resource ('this site's location'), and the target system ('credentialcamp connection'). Naming credentialcamp distinguishes it from other linked-location siblings, though it does not explicitly contrast with them.

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?

Usage is implied by 'this site's location in the existing credentialcamp connection,' but there is no explicit when-to-use or when-not guidance. The many sibling linked-location tools are not mentioned as alternatives, and the approval notes describe prerequisites rather than selection criteria.

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?