Skip to main content
Glama

hjarni

by com.hjarni
OverviewDiscussionsAdmin

teams-invite

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'). Inviting is always free; on a team that already subscribes, each person who joins adds a billable seat straight away.

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.9/5.0
Behavior5/5

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

The description discloses substantial behavioral details beyond the annotations: creating a link replaces any existing one ('REPLACES any existing one'), the 'revoke' action removes it, and joining adds a billable seat. It also warns to give the link to the user, never post it. Annotations only indicate mutation (readOnlyHint=false), but the description adds crucial side effects and usage constraints.

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?

The description is long but logically structured, starting with purpose and required parameters, then modes, guidance, caveats, and pricing. Each sentence adds operational value with no repetition. Slightly verbose, but the density of information justifies the length.

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?

Covers all necessary context: permission (team owner only), both modes with their outputs (join_url, expires_at, uses_remaining), side effects (replacement, billing), and edge cases (reusing a shared link). The description is complete for an agent to call the tool correctly without an output schema.

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

Parameters5/5

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

While the schema covers all three parameters, the description adds strategic semantic guidance: it explains the email vs. no-email decision, clarifies that 'action' only applies to link mode, and specifies that team_id comes from teams-list. This goes beyond simple schema definitions to guide the agent's parameter selection.

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 tool's purpose with a specific verb and resource: 'Get a teammate into a team'. It distinguishes two operational modes (email vs. join link) and explicitly notes the 'team owner only' permission. It also references sibling tool 'teams-list' for obtaining team_id, making it easy to differentiate from other team-related tools.

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?

Provides explicit guidance on when to use the link vs. email: 'Prefer the LINK unless the user names an address'. Critically, it directs users away from this tool when repeating a shared link: 'read join_url from teams-get instead of calling this'. This is a clear, actionable alternative.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources