Skip to main content
Glama
Heliyos MCP server

Heliyos MCP server

Official
by heliyos-ai

Invite a team member

heliyos_team_members_invite

Sends an email invitation to join a Heliyos workspace with an ADMIN or MEMBER role. Check existing team members first to avoid conflicts with pending invitations.

Instructions

Emails an invitation to join the workspace with the given role (ADMIN or MEMBER). A second invite to an email with a pending invitation fails with CONFLICT (resend it from Heliyos), so check heliyos_team_members_list first. Returns structuredContent {member} with the new membership_id and status invited.

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>",
      "role": "<role>"
    },
    "name": "heliyos_team_members_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYesADMIN or MEMBER. OWNER cannot be granted with an API key; an owner does that in Heliyos Settings, Team.
emailYesThe person's email address.

Output Schema

NameRequiredDescriptionDefault
memberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-idempotent, non-destructive, closed-world behavior; the description adds real value beyond that by naming the CONFLICT failure mode on duplicate invites and pointing to the recovery path. It stops short of stating who may invite (required permission/scope) or whether a sent invite can be revoked, which matters for a mutation tool that triggers an outbound email.

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?

Three tight sentences with no filler: action first, precondition and failure mode second, return shape last. Every clause carries operational information.

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 two-parameter mutation with full schema coverage, annotations, and an output schema, nothing an agent needs to call it correctly is missing; the callback of return shape is mild redundancy but harmless.

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 100%, so the role enum, the OWNER restriction, and the email format are all already documented. The description only restates the role values, adding no format, constraint, or edge-case detail the schema does not already carry — baseline 3 applies.

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?

States a specific verb and resource ('Emails an invitation to join the workspace') plus the role scope, which is unmistakably distinct from siblings like heliyos_team_members_change_role or heliyos_team_members_list. An agent can select this tool 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 Guidelines5/5

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

Gives an explicit precondition ('check heliyos_team_members_list first') and names the correct alternative path for the failure case ('resend it from Heliyos'), so the agent knows both when to call this and what not to retry.

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

Deploy Server

Other Tools