LFG Alarm

Get a link to add a file

get_upload_link

Makes a one-time lfg.gm page link for putting a file from the person's own device on an alarm they made: a picture or short video as the wallpaper, a song, or a voiceover. For a file only on the person's own device; a file at a public link, or one this AI app has in hand, can go on directly. On the page the person picks the file, or for a voiceover records their voice; it lands on the alarm when they finish. The link works once, for an hour. Returns the page link and a direct address a file can be sent to. What each takes. Wallpaper: a square (1:1) picture, about 1080 x 1080 pixels, as JPEG, PNG, WebP or GIF up to 50MB; a picture that is not square is cropped to a square. Or a square MP4 or MOV video, or a GIF that loops, up to 30 seconds and 50MB; a video needs a paid plan, a GIF does not. Song or voiceover: MP3, M4A, OGG, WAV or FLAC up to 5 minutes and 20MB.

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": {
      "id": "<id>",
      "use": "<use>"
    },
    "name": "get_upload_link"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The alarm's id.
`use`	Yes	wallpaper (picture or short video), song, or voiceover (a voice message).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only flag it as a non-read-only, non-idempotent write; the description adds the genuinely useful behavioral facts: the link is single-use ('The link works once, for an hour'), the user completes the upload on an external page, and it returns both a page link and a direct address. It also discloses a plan-gated constraint (video requires a paid plan, GIF does not), none of which is derivable from annotations.

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 core purpose and the one-time/expiry behavior, then organizes the format rules by use type. It is information-dense with no filler, though the long single-block format section and fragment 'What each takes.' make it slightly tiring to parse.

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

Completeness5/5

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

With no output schema, the description still covers the return values ('the page link and a direct address a file can be sent to'), the interaction flow (user picks/records on the page), expiry semantics, and exhaustive per-use file constraints. Nothing essential for correct invocation is missing.

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 100%, so the baseline is 3, but the description substantially enriches the 'use' enum by giving per-value constraints: wallpaper needs square 1:1 ~1080x1080 JPEG/PNG/WebP/GIF up to 50MB (or MP4/MOV/GIF up to 30s), while song/voiceover needs MP3/M4A/OGG/WAV/FLAC up to 5 minutes and 20MB. It adds little about the 'id' parameter beyond the schema, hence not a full 5.

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: 'Makes a one-time lfg.gm page link for putting a file from the person's own device on an alarm they made', and enumerates the target uses (wallpaper, song, voiceover). It also distinguishes itself from siblings by declaring the scope: 'For a file only on the person's own device; a file at a public link, or one this AI app has in hand, can go on directly', which separates it from add_media_from_url and add_media_file.

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?

Clear when-to-use (file lives only on the user's device) and when-not (public-link or already-ingested files 'can go on directly'), which routes the agent away from this tool in those cases. It stops short of naming the alternative siblings, so the routing requires a small inference about which tool handles the direct path.

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

All LFG Alarm tools Inspect

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.