RetailHardHat

Invite Team Member

invite_team_member

Invite a person by email as an organization member or admin. Sends a real email and grants the reviewed role upon acceptance. Replaces a prior pending invitation for that email. Cannot grant platform privileges. 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": "invite_team_member"
  }
}

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

A4.5/5.0

Behavior5/5

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

This description provides rich behavioral transparency that annotations cannot capture. It informs the user that the process is subject to configurable 'MCP approval requirements' and mandatory 'business workflow approvals,' which are critical operational details.

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 extremely efficient, consisting of two sentences where every phrase adds functional value (e.g., 'Grants the reviewed role upon acceptance,' 'Cannot grant platform privileges').

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?

For a complex orchestration task like organizational invitation, the description is complete. It covers the scope (organizational), the mechanism (email/acceptance), the limits (no platform privileges), and the governance structure (workflow approval), leaving no major ambiguity for the AI.

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?

While schema coverage is 0%, the description provides high-level context for the core inputs (email, role). However, it does not explain the purpose or intended use of the optional 'message' parameter beyond the general 'sends a real email' statement, making it a moderate description.

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 stated clearly: inviting a person by email as an organization member or admin. Given the massive list of sibling tools (e.g., add_project_team_member, add_site_team_member), the description successfully narrows the scope to organizational roles, providing excellent differentiation.

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?

The description provides important usage context by explaining that the role is granted upon email acceptance. Furthermore, it handles a crucial edge case by stating that the tool 'Replaces a prior pending invitation for that email,' which helps prevent redundant calls.

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?