Skip to main content
Glama

LFG Alarm

by gm.lfg
OverviewDiscussionsAdmin

Set a trader alarm

set_trader_alarm

Sets an alarm that rings on the person's phone when a trader buys, sells or posts a thesis, when anyone on FOMO trades a token, or when a wallet buys or sells. For trades by a person, a wallet or anyone in a token; a token reaching a price is a different alarm. Takes exactly one of: a trader's handle (on FOMO, or a KOL GMGN tracks by X handle), a token's contract address, or a wallet address on Solana or an EVM chain. A thesis is on FOMO only, and a wallet alarm is never public. After ringing it stays quiet for 15 minutes, so a run of trades is one ring. Returns the alarm and its link.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoA note from the person about the alarm, in their words, shown under its trigger on the alarm's page and in the Daily drop. Up to 500 characters; an empty note clears it.
vibeNoThe feel of the alarm in a few words, "fun poppy anime", "calm", "a simple bell", "hype for a token launch". LFG picks a sound and a drawn look from its library to match; wallpaper words or colours given here win over the look.
reachNoWho can join: private (only the person), friends (people on its list, or with its link), public (anyone; listed in Discover).private
themeNoA picture theme: the alarm gets one of the theme's pictures as its wallpaper and a song in its moods, and a new alarm a title written for it. A wallpaper, title or vibe given as well is kept instead. One of: birthday (Birthday), love (Love), night_out (Night out), shopping (Shopping), winter (Winter), christmas (Christmas), hanukkah (Hanukkah), diwali (Diwali), halloween (Halloween), thanksgiving (Thanksgiving), friendsgiving (Friendsgiving), new_years (New Year's Eve).
titleNoShort name for the alarm. When absent, LFG names it. Up to 60 characters; it reads best under about 25.
watchNoWhat rings it. A thesis (a trader's written case for a token) is on FOMO only.
sourceNoFor a trader on both: fomo watches their FOMO trades and theses, gmgn watches the wallets GMGN tracks for them. FOMO when absent.
traderNoA trader's handle, "frankdegods". LFG looks for it on FOMO, then among the KOLs GMGN tracks by X handle.
min_usdNoThe smallest trade that rings it, in US dollars, any amount. Each source has a least it can see, and an amount under it is raised to it: FOMO from $3,000 (its feed carries buys from about there; a sell carries no size, so every sell by a watched trader counts), default 10000. GMGN from $100, default 500. A wallet from $50, default 5000.
surpriseNoFor a friends alarm: keep it a surprise. People who join see a curtain instead of its title, picture, sound and note until it rings. Free on every plan.
add_groupsNoFor a friends alarm: names of the person's friend groups whose members to let in, "Family". Members get a notification.
add_peopleNoFor a friends alarm: up to 20 people to let in, as usernames of the person's LFG friends or as email addresses. Friends get a notification; an email address with no LFG account gets an invitation. Any other username is refused.
button_linkNo
words_colorNoColour of the words as hex, any colour, "#D7FF00". Pick one that stands out from the background.
hide_triggerNoNeeded with surprise, true or false: whether to also keep back when and why it rings, so people who join only know that it will. A surprise is not made until it is given.
snooze_timesNoHow many times it can be snoozed: 3, 10 or unlimited.
silent_snoozeNotrue to snooze without the spoken roast LFG plays by default.
token_addressNoA token's contract address: rings when anyone on FOMO trades it.
snooze_minutesNoMinutes each snooze lasts: 5, 10, 15, 30 or 60.
wallet_addressNoA wallet's address, Solana or EVM (0x...): rings when it buys or sells.
wallpaper_colorNoWallpaper background colour as hex, any colour, "#5B2BFF".
wallpaper_wordsNoWords drawn on the wallpaper, "WAKE UP"; a line break starts a new line. Up to 40 characters; it looks best as 1 to 4 short words, since the words are drawn as large as the square allows.
people_confirmedNoWhether the person has confirmed the people and groups being added. Nobody is added or told without it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / title / description
      Previous value: -"Short name for the alarm. When absent, LFG names it."New value: +"Short name for the alarm. When absent, LFG names it. Up to 60 characters; it reads best under about 25."
    • changedInput schema / properties / title / maxLength
      Previous value: -120New value: +60
    • changedInput schema / properties / wallpaper_color / description
      Previous value: -"Wallpaper background colour as hex, \"#5B2BFF\"."New value: +"Wallpaper background colour as hex, any colour, \"#5B2BFF\"."
    • changedInput schema / properties / wallpaper_words / description
      Previous value: -"Words drawn on the wallpaper, \"WAKE UP\"; a line break starts a new line."New value: +"Words drawn on the wallpaper, \"WAKE UP\"; a line break starts a new line. Up to 40 characters; it looks best as 1 to 4 short words, since the words are drawn as large as the square allows."
    • changedInput schema / properties / wallpaper_words / maxLength
      Previous value: -80New value: +40
    • changedInput schema / properties / words_color / description
      Previous value: -"Colour of the words as hex, \"#D7FF00\"."New value: +"Colour of the words as hex, any colour, \"#D7FF00\". Pick one that stands out from the background."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: exactly-one-of targeting constraint, thesis alarms are FOMO-only, wallet alarms are never public, and a 15-minute quiet period after ringing so a run of trades collapses into one ring. It also discloses the return ('the alarm and its link') which matters since no output schema exists.

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-loaded with the trigger model, then the exclusivity rule, then cooldown and return value — every sentence carries information, none is filler. It is dense for a single paragraph but justified by the tool's breadth; slight tightening of the trader/token/wallet enumeration would help.

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 23-parameter, zero-required, no-output-schema mutation tool, the description covers what the tool does, how the target is chosen, cooldown behavior and what it returns, with annotations carrying the safety profile. The many presentation parameters (theme, vibe, wallpaper, snooze) are left to the schema, which is reasonable given 96% coverage, but the description never signals that such customization exists.

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?

Schema coverage is 96%, so the baseline is 3, but the description adds a genuinely non-schema constraint: exactly one of trader, token_address or wallet_address must be supplied, which is not expressed as a top-level oneOf in the schema. It also clarifies the FOMO-only restriction on the thesis watch value beyond the schema's brief note.

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 (sets), resource (alarm) and the exact trigger semantics: a trader buying/selling/posting a thesis, anyone on FOMO trading a token, or a wallet buying/selling. It actively distinguishes itself from the sibling price alarm ('a token reaching a price is a different alarm') so an agent can separate it from set_price_alarm without opening either schema.

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 conditions for the three mutually exclusive targeting modes (trader handle vs token contract address vs wallet address) and states the exclusion against price alarms. It does not name the other alarm siblings (set_time_alarm, set_event_alarm, set_webhook_alarm) that a confused agent might also consider, so guidance is strong but not fully exhaustive.

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