PinAppAI

invite_member

Invite a user to the API key's workspace as admin / editor / viewer (default editor). Admin role required to call. Sends a welcome email.

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": {
      "email": "<email>"
    },
    "name": "invite_member"
  }
}

Input Schema

Name	Required	Description
`name`	No	Optional display name; defaults to the email's local-part.
`role`	No	Defaults to editor. Admins can't invite owners — that requires an existing owner.
`email`	Yes	Invitee's email address.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 20, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The description adds context beyond annotations by specifying the required admin role and the email side effect. There is no contradiction with annotations (idempotentHint=false, destructiveHint=false). However, it does not mention idempotency or destructibility.

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?

Two concise sentences with no wasted words. The first sentence covers purpose and roles; the second covers prerequisites and side effects. Front-loaded and efficient.

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?

For a simple invitation tool with few parameters and no output schema, the description is sufficiently complete. It covers purpose, roles, prerequisites, and side effects. Could optionally mention the return value, but not essential.

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

Parameters4/5

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

All three parameters are already described in the schema (100% coverage). The description adds value by clarifying the default role ('default editor') and the default for the 'name' parameter ('defaults to the email's local-part').

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 description clearly states the action ('Invite a user'), the target resource ('the API key's workspace'), and the allowed roles ('admin / editor / viewer'), distinguishing it from the sibling tool 'invite_reviewer' which likely invites external reviewers.

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 explicitly states the prerequisite ('Admin role required to call') and the side effect ('Sends a welcome email'), but does not provide guidance on when not to use the tool or mention alternatives like 'invite_reviewer'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PinAppAI tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?