Skip to main content
Glama
Sign In

LFG Alarm

by gm.lfg
OverviewDiscussionsAdmin

Use an invite code

use_invite_code
Destructive

Uses a friend's LFG referral code for the person: it records who brought them in and makes them friends on LFG. For a referral code (LFG-…); an alarm's link or code is joined, not used here. Once per account and never their own code; it cannot be undone. The welcome gift opens for both when the person's first alarm rings. A code that is not one returns an error.

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": "use_invite_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe referral code, "LFG-AB12C", or an invite link (lfg.gm/i/...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The annotations already mark this as destructive, non-idempotent, and open-world. The description adds substantial behavioral context beyond that: the action cannot be undone, is limited to once per account, rejects the person's own code, triggers a welcome gift when the first alarm rings, and returns an error for invalid codes.

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 front-loaded with the core action and effect, and most sentences carry useful constraints or behavioral details. It is somewhat dense and uses semicolon-heavy phrasing, but it is not bloated.

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 one-parameter mutation with rich annotations and no output schema, the description covers purpose, restrictions, irreversibility, side effects, and error behavior well. It could be more complete by explicitly acknowledging invite-link inputs and success behavior.

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?

There is only one parameter and schema description coverage is 100%, so the schema already defines the code format and examples. The description adds that invalid codes error, but it does not meaningfully extend the parameter semantics beyond the schema and is slightly ambiguous about invite links that the schema says are accepted.

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 states a specific verb and resource: using a friend's LFG referral code for a person, recording who referred them and creating a friendship. It also distinguishes this from joining an alarm via an alarm link or code, so an agent can tell it apart from sibling tools like join_alarm.

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?

It gives clear context for when this applies: referral codes in the LFG- format, once per account, never one's own code. It also excludes alarm links/codes as something that is 'joined, not used here,' though it does not explicitly name the sibling tool to use instead.

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

All LFG Alarm 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