Skip to main content
Glama

invite_client_to_organization

Invite a client to join the organization by email, optionally pre-assigned to a coach and location (confirm-gated). They receive a real 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": {
      "organizationId": "<organizationId>",
      "email": "<email>"
    },
    "name": "invite_client_to_organization"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYes
coachIdNo
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
locationIdNo
expiresInHoursNo
organizationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare the non-read, non-destructive profile; the description adds that execution is confirm-gated and that a real email is sent to the client, which is the key consequence an agent must anticipate. It stops short of describing duplicate-invite behavior or what the preview returns.

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 short sentences, front-loaded with the action and scope, with the side effect and gate in the second. No filler or redundancy.

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?

A six-parameter mutation tool with no output schema needs more than this: the expiry control, the preview result, and error/duplicate handling are uncovered. The critical safety fact (confirm gate, real email) is present, so it is adequate but with clear gaps.

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?

Schema description coverage is only 17% (only `confirm` is documented), so the description carries most of the burden. It usefully explains coachId/locationId as pre-assignment, but says nothing about expiresInHours, which remains undocumented in both places.

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?

States a specific verb and resource ('Invite a client to join the organization by email') and names its differentiator from the coach sibling by specifying the invitee type. The optional coach/location pre-assignment is also named, so an agent can tell it apart from invite_coach_to_organization without opening the schema.

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 only implied: it invites a client, so it is not the bulk (bulk_invite_clients), link-based (create_invite_link), or staff paths. No explicit when-to-use/when-not-to-use guidance or named alternative appears in the description.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.