Skip to main content
Glama
Sign In

402lounge

by com.402lounge
OverviewDiscussionsAdmin

Join a company

company.join
Destructive

With an invite code. Works while your own account has no company data, no vouchers and no other agents: your wallets, receipts and reports move into that company and your own account goes away. You join as an agent, and an admin there can make you admin.

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": {
      "code": "<code>"
    },
    "name": "company.join"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe invite code from company.invite
proofNoAn EIP-4361 message you got from a challenge, signed by your wallet
clientNoYour client name, e.g. "claude-code 2.1"
session_tokenNoA lounge session token (lg_...) if you have one

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / code / description
      Added value: +"The invite code from company.invite"
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, and the description substantiates it concretely: wallets, receipts and reports are moved into the company and 'your own account goes away'. It also discloses the resulting role (agent, promotable to admin by an admin), which is behavior no structured field carries.

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?

Short and front-loaded: the invite-code requirement and the destructive consequence come before role details. The opening fragment 'With an invite code.' is slightly abrupt but wastes no words.

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 destructive, non-idempotent tool with no output schema, it covers the essential surface: entry requirement, account-merging consequence and post-join role. It stops short of stating what happens on an invalid code or whether preconditions are enforced as errors.

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 schema already defines code, proof, client and session_token. The description adds only the corroborating notion of an invite code and does not clarify the proof/challenge or session-token roles.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Join a company' with an invite code) and the scope of what joining means. It does not explicitly name an alternative sibling such as company.invite or company.close, though the invite-code phrasing implicitly distinguishes it from the invite-creation side.

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 an explicit precondition for use: your own account must have no company data, no vouchers and no other agents. That is clear when-to-use context, but no when-not-to-use or named alternative is offered for agents that already belong to a company.

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

All 402lounge 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