Skip to main content
Glama

Invite someone to a company

company_invite_create

Sends an e-mail invitation to join one of your companies with a role (viewer, member, admin or owner). Owners can invite any role; admins only member or viewer. The invitation expires in 7 days; the link is only in the e-mail and is not shown here. A company can have at most 25 members including pending invitations. Call without confirm first for a preview, then again with confirm and the preview_token.

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": {
      "company": "<company>",
      "email": "<email>",
      "role": "<role>"
    },
    "name": "company_invite_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes
emailYesE-mail address of the person to invite.
localeNoLanguage of the invitation e-mail. Default en.
companyYesCompany ref (CO-XXXXXXXX) from company_list_mine.
confirmNoSet true only on the second call, after the user approved the preview.
preview_tokenNoThe preview_token returned by the first call (same input).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, destructive=false, idempotent=false), the description discloses that a real e-mail is dispatched, the invite expires after 7 days, the acceptance link is delivered only in the e-mail and is never returned, and a company is capped at 25 members including pending invites. These are exactly the side effects and limits an agent cannot infer from the structured fields.

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?

Four short sentences, no filler, each carrying distinct constraints (roles and permissions, expiry and link delivery, member cap, confirm flow). The two-step calling instruction is placed last so the constraints are understood before the agent acts.

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 mutating invite tool with no output schema, it covers everything an agent needs: side effect (e-mail sent), irreversibility (link not returned here), expiry window, seat-limit precondition, role authorization, and the confirm handshake. Nothing material is left to guesswork.

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?

Schema coverage is high (83%) and already documents each field, but the description adds real meaning to the confirm/preview_token pair by explaining they implement a preview-then-commit confirmation, and it clarifies role choices and the resulting permission levels. It leaves locale entirely to the schema, so it is not fully additive on every parameter.

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 opens with a specific verb and resource: 'Sends an e-mail invitation to join one of your companies with a role'. It enumerates the four roles and the tool's scope (an invite, not a membership change), which clearly separates it from siblings like company_invite_resend, company_invite_revoke, and company_member_role_set.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit two-step invocation flow: 'Call without confirm first for a preview, then again with confirm and the preview_token.' It also states the permission precondition (owners may invite any role, admins only member or viewer), so the agent knows both the sequence and the eligibility gate before calling.

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.

Resources