Skip to main content
Glama
Sign In

LFG Alarm

by gm.lfg
OverviewDiscussionsAdmin

Put a library item or upload on an alarm

set_media
DestructiveIdempotent

Puts something already in LFG on an alarm the person made, by its id: a library sound, a SoundCloud song that plays in full, a drawn or live look or a theme picture, or one of the person's own uploads. For something already in LFG with an id; a new file goes on by link, as a file, or through the one-time page, and a KLIPY GIF by its address. use says where it goes: the wallpaper, the song, or the voiceover (the person's own sounds only). It replaces what that slot had. An id that matches nothing 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": {
      "id": "<id>",
      "use": "<use>",
      "media_id": "<media_id>"
    },
    "name": "set_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe alarm's id.
useYeswallpaper, song, or voiceover.
media_idYesA library sound's id, a SoundCloud song's id (soundcloud:track:N, from find_soundcloud_song) or its link, a drawn or live look's id, a theme picture's address, or an upload's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / media_id / description
      Previous value: -"A library sound's id, a drawn or live look's id, a theme picture's address, or an upload's id."New value: +"A library sound's id, a SoundCloud song's id (soundcloud:track:N, from find_soundcloud_song) or its link, a drawn or live look's id, a theme picture's address, or an upload's id."
  2. Changed1 schema field changed
    • changedInput schema / properties / media_id / description
      Previous value: -"A library sound's id, a drawn look's id, or an upload's id."New value: +"A library sound's id, a drawn or live look's id, a theme picture's address, or an upload's id."
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the mutation profile is known. The description usefully adds what is destroyed — it replaces whatever occupied that slot — plus that the named person must own the alarm and that a non-matching id returns an error, but says nothing about permissions, return value, or cross-slot side effects.

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?

Purpose is front-loaded in the first clause and no sentence is filler, but the phrasing is wordy and run-on ('the person made', 'the person's own sounds only' repeated) where a tighter list of accepted id kinds and slot values would read faster.

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 3-required-parameter mutation with no output schema, it covers the essentials: accepted id forms, the three slot values and their constraint, replacement semantics, and the not-found error. Only the failure modes beyond 'id matches nothing' and any ownership/permission requirements are left unstated.

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 coverage is 100%, so all three parameters are already documented, and the description largely restates them. It does add two things the schema lacks: the voiceover slot accepts only the person's own sounds, and SoundCloud ids come from find_soundcloud_song in soundcloud:track:N form — meaningful but marginal over a fully documented schema.

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 concrete verb and resource: it attaches an already-existing LFG item (library sound, SoundCloud song, look, theme picture, upload) to an alarm, keyed by id. The second sentence draws a boundary against the new-file paths (link upload, file upload, one-time page, KLIPY GIF), so an agent can separate this from set_gif and the add_media_* family, though it never names those siblings explicitly.

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 when-to-use routing: use this only for things already in LFG that have an id, and use the link/file/one-time-page paths otherwise, with KLIPY GIFs going by address. It stops short of naming the competing tools (add_media_file, add_media_from_url, get_upload_link, set_gif), so the agent must map described alternatives to sibling names itself.

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