Skip to main content
Glama

hjarni

by com.hjarni
OverviewDiscussionsAdmin

teams-invite

Destructive

Get a teammate into a team (team owner only), two ways. Required: team_id (integer, from teams-list). WITH email: emails an invite to that address. WITHOUT email: returns join_url, a shareable link anyone can open to join themselves, plus join_link_expires_at and join_link_uses_remaining. Prefer the LINK unless the user names an address — few people can recall a colleague's address mid-conversation, and asking is where teams stall at one member. Give the link to the USER to share; never post it anywhere yourself. Creating a link REPLACES any existing one, so to repeat a link already shared, read join_url from teams-get instead of calling this. Optional: action ('create' (default) | 'revoke').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNoAddress to email an invite to. Omit to get a shareable join link instead.
actionNoLink mode only (no email): 'create' (default) mints a link and invalidates any previous one; 'revoke' removes it.
team_idYesTeam ID (required; use teams-list to find it)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / description
      Previous value: -"Invite a teammate to a team by email."New value: +"Invite a teammate by email, or get a shareable join link."
    • addedInput schema / properties / action
      Added value: +{
+  "description": "Link mode only (no email): 'create' (default) mints a link and invalidates any previous one; 'revoke' removes it.",
+  "enum": [
+    "create",
+    "revoke"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / email / description
      Previous value: -"Email address to invite (required)"New value: +"Address to email an invite to. Omit to get a shareable join link instead."
    • changedInput schema / required
      Previous value: -[
-  "team_id",
-  "email"
-]New value: +[
+  "team_id"
+]
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: notes it is team-owner-only (auth requirement), warns that 'Creating a link REPLACES any existing one' (matching destructiveHint/idempotentHint=false), and instructs the agent never to post the link itself. This enriches the destructiveHint=true signal with the specific resource that gets invalidated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Information-dense and front-loaded, with the mode split and required parameter stated first. It runs long, but nearly every clause carries operative detail (mode selection, replacement warning, sharing rule) rather than filler.

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?

With no output schema, the description compensates by naming the returned fields (join_url, join_link_expires_at, join_link_uses_remaining) and warning about link replacement. An agent has everything needed to call it and interpret the result correctly.

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 100%, so the baseline is 3, but the description adds real semantics: email omission switches to link mode, action defaults to 'create', and 'revoke' removes the link. It also explains the side effect of 'create' (invalidating prior links), which the schema only hints at.

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 ('Get a teammate into a team') and enumerates the two operating modes (with email vs. without). It explicitly references team_id provenance (from teams-list) and distinguishes itself from teams-get by explaining read vs. create semantics for join links.

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 default preference ('Prefer the LINK unless the user names an address') with a rationale, and names the alternative path (read join_url from teams-get to re-share rather than re-minting). This is actionable when/when-not guidance rather than implied context.

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

All hjarni toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources