Skip to main content
Glama

writ_tenant_invite

Mint a team invite code (writ_inv_...) for your tenant.

Instructions

Mint a team invite code (writ_inv_...) for your tenant.

Share the code with teammates: they pass it as invite_code to writ_join_tenant (POST /v1/keys) to join this tenant instead of creating their own. Creating a new code ROTATES and invalidates the old one, so there is only ever one live invite code per tenant, and only mint when the team needs a fresh code.

Returns the gate payload verbatim: inviteCode, tenantId, and a note.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "writ_tenant_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.20

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the destructive side effect that 'Creating a new code ROTATES and invalidates the old one,' plus the invariant that only one live code exists per tenant. It does not state required permissions or role (e.g. whether only an admin can mint), which is the main remaining gap for a state-mutating tool.

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?

Front-loads the core action and the code prefix, then follows with usage, the rotation warning, and the return payload in a logical order. Every sentence is substantive, though the trailing 'Returns the gate payload verbatim' sentence overlaps with the existing output schema and could be trimmed.

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?

For a zero-parameter mutation tool with an output schema, the description covers the essential unknowns: the invalidation of prior codes, the single-live-code invariant, and the downstream consumer. Only authorization requirements are missing, which is a minor omission given the output schema already documents return fields.

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?

The tool takes zero parameters, so there is no parameter meaning to add and the baseline of 4 applies. The description correctly does not invent parameters and instead spends its words on effects and return payload.

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 ('Mint a team invite code (writ_inv_...) for your tenant') and includes the code prefix, which makes the artifact identifiable. It also names the counterpart tool (writ_join_tenant) that consumes the code, so an agent can distinguish this from the join flow without opening schemas.

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?

Explicitly says when to use it ('share the code with teammates'), how the output is consumed ('they pass it as invite_code to writ_join_tenant (POST /v1/keys)'), and gives a when-not-to constraint ('only mint when the team needs a fresh code'). The alternative path (teammates creating their own tenant) is contrasted directly.

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