Skip to main content
Glama

QueryMind

Invite a colleague

invite

Administrators can create a single-use invitation link valid for 24 hours. Share the link yourself; this tool does not send email. The recipient signs in or signs up through the link and uses the same connector address.

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

Input Schema

NameRequiredDescriptionDefault
roleNoRole in the organization; defaults to analyst.
emailYesRecipient email, which becomes their login ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only mark this as a non-read-only, non-idempotent, non-destructive write; the description adds the materially useful facts that the result expires in 24 hours, is single-use, and that no email delivery occurs. It does not cover behavior for a recipient who already has an account or how many links may be outstanding, which keeps it below the top score.

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 short sentences, front-loaded with what is created, followed by the operational caveat and the recipient flow. Every sentence conveys information an agent would otherwise have to guess.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two parameters, full schema coverage, and annotations present, the description covers nearly everything needed. The one remaining ambiguity is how the administrator obtains the link (i.e., whether it is returned in the response), which the description implies ('Share the link yourself') but never states outright in the absence of an output schema.

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 both parameters (email, role) are already documented, including the role default and enum values. The description adds no syntax or format guidance beyond the schema, so the baseline of 3 applies despite the phrase about the connector address.

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+resource: 'create a single-use invitation link', and adds the two constraints that define it (single-use, 24-hour validity). An agent knows exactly what this produces without consulting anything else, and no sibling in the list performs a comparable invitation action.

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

Usage Guidelines4/5

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

Gives clear preconditions ('Administrators can...') and the critical usage note that the link must be shared manually because no email is sent. It also describes the recipient's flow ('signs in or signs up through the link'). It does not explicitly state when not to use it, but no plausible alternative is present in the sibling set.

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